Yesterday I identified playmaker adds unwanted permissions to AndroidManifest.xml.
=> example:
I have a project without any playmaker asset imported, working and an existing AndroidManifest.xml (under Assets/Plugins/Android/) with some wanted permissions. If I publish this project everything works fine, the AndriodManifest.xml will stay the same and permissions are like expected!
Now I just import playmaker asset from asset store, without even using playmaker in my project (no fsm, no actions, nothing) and automatically these lines will be added to AndroidManifest.xml while publishing:
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-feature android:name="android.hardware.location.gps" android:required="false" />
<uses-feature android:name="android.hardware.sensor.accelerometer" />
<uses-feature android:name="android.hardware.touchscreen" />
<uses-feature android:name="android.hardware.touchscreen.multitouch" android:required="false" />
<uses-feature android:name="android.hardware.touchscreen.multitouch.distinct" android:required="false" />
You can find the new one which will be used in your app under "assets/temp/StagingArea/", the old one is renamed to AndroidManifest-main.xml.
Why does Playmaker add all these permissions I dont use or want?
Problem is that publishing a apk make no sense any more because new manifest file will be used...
How to forbid playmaker to add anything to AndroidManifest.xml?
Thanks in advance!