Over17
commented
8 years ago Hi!
What is the targetSdkVersion in your final manifest? (I assume it is 23).
Here is what happens: When 23 is selected as target API level, Marshmallow enables the new permission system (http://developer.android.com/about/versions/marshmallow/android-6.0.html). This means all dangerous permissions are by default denied. Your app has to ask user for the permissions before they are actually granted. In your case, WRITE_EXTERNAL_STORAGE permission is missing. You could check that by going to Settings > Apps > yourapp > Permissions.
A simple dialog asking for all dangerous permissions is shown on startup in later versions of Unity. Best option for Unity 4 is to use the latest 4.7.0 - it has this dialog as well as a number of fixes.
If you cannot update your Unity to later versions, here are the options I see:
- limit targetSdkVersion to 22. This disables the Marshmallow permission system. Downsides: your app won't get featured; if you already published the app with target level 23, it won't allow you to "downgrade" it.
- write a Java plugin to prompt the user for the permissions. You could even do a runtime check for permissions if you trust your plugins. Please consult Android developer website or search a sample yourself.
Hope that helps.
spl0k
qbit86
Hi.
I'm observing some weird behaviour on devices running Android 6.0. Our app is published on the Google Play Store. If we run it right after downloading and installing it from there Unity doesn't seem to find the obb file while the plugin returns a path. This cause our app to be stuck on the first loading screen.
I've searched around, and I'm not sure if this is related to the new permission system (#5). logcat doesn't show any error on that matter. Strangely enough, after rebooting the device the problem is gone and the app runs without issue.
Is this really a permission issue? We're using Unity 4.6.4f1 (a bug in later versions prevents us from upgrading)