Playmaker Forum

PlayMaker Help & Tips => PlayMaker Tips & Tricks => Topic started by: smiffy on July 17, 2012, 05:02:41 PM

Title: DeviceVibrate action and Nook/Kindle AndroidManifest woes
Post by: smiffy on July 17, 2012, 05:02:41 PM

So last week we we're getting our app refused from the Nook store as the line <uses-permission android:name="android.permission.VIBRATE" /> was being generated by Unity in the androidManifest.xml and vibrate is not allowed on the nook (or Kindle either).

Turns out just having DeviceVibrate.cs in the actions folder causes this, you don't have to have used it.

So delete it and Unity automatically removes it on build. You can check in the stagingArea folder in your Main project folder.

Hope this helps.

Title: Re: DeviceVibrate action and Nook/Kindle AndroidManifest woes
Post by: Alex Chouls on July 23, 2012, 01:01:31 AM

Thanks! Good to know.

We hope to add an Optimize Build option in Playmaker soon that will automatically delete all actions not used in your project. Until then you have to delete actions manually in cases like this, or if you want to make the exe a bit smaller...