- Obb file editor apk apk#
- Obb file editor apk install#
- Obb file editor apk update#
- Obb file editor apk code#
- Obb file editor apk download#
Maybe one day google will remove their apk size limit and we won't ever have to deal with this again.ĮDIT: Just wanted to quickly mention that this android bug sometimes does not occur. If you upload a new obb into that folder, it should also have root permission, which is great, because it means you can test the permissions locally without uploading an alpha/beta build on google play. Note that you won't be able to test with this obb, since obb's must match the apk they were built with. The old obb should still be there with root permissions.
Obb file editor apk install#
Now, install an updated apk and replace the old one (make sure the version codes of both apks are the same). Your obb file should have "root" as the owner, which means the app can't read it without permission.
Obb file editor apk download#
First, you download the app from the play store and reproduce the bug. Oh, and you can test the changes locally without having to wait 5 hours to upload to Google Play.
Obb file editor apk code#
Here's the code for that Our app is now live and everything seems to be going well. The app will be restarted again once the alarm is activated. You can do this in java by setting a PendingIntent alarm to start the app up in X seconds and then exiting the app immediately. This seems like a bug in the plugin though, it should probably flush first and then call the callbacks.Įdit: We ended up actually having to restart the app after accepting read permissions for the first time as we were getting extremely odd bugs - UI elements were sometimes getting loaded and sometimes not, even for the same assets. I think this is because the actual permissions are flushed only after the callbacks are called. If you don't, the obb will not be correctly loaded.
Obb file editor apk update#
Had to write a native android plugin for that, you can find the code here Īnother thing is that if you're using the UnityAndroidPermissions plugin ( ), after receiving the permission granted callback, you should wait til the next Update loop to actually change scenes. This extra check is good so that devices that don't have this bug won't need to ask for the READ_EXTERNAL_STORAGE permission. If the primary obb file can be read, then we shouldn't need to ask for any permissions. In our game, we check if the primary obb file can be read, and if it can't, then the permissions dialog will popup. The bug should be fixed in Nougat and above (at least according to the documentation here ()), but apparently it still occurs for some people. Just to expand on DaReign's answer for anyone else who needs to go through this pain: Remove the need to use OBB expansion files I say, life would be much simpler. Other android based platforms around the world don't have this horrible 100mb apk limitation and these large apk files install and run perfectly fine. This issue I've spent weeks researching different work arounds, it's my single biggest annoyance with the android SDK and I believe Google could completely solve it in a retroactive way if they'd allow single apk installations over 100mb and they simply reworked how the over the air 100mb installation limitation is enforced, they already have a warning popup when you're using mobile data so there's no reason for this apk file size limitation anymore. But having the write external storage permission there negates the issue, however it will unnecessarily add horrible user facing permissions to your play store listing. Restarting resolves the file permissions. The problem is that the obb file does get stored but doesn't have the correct user permissions so is unreadable by the app. But in android 6 there was a regression bug that brought the issue back. In API 19 they removed the need to ask for this permission to store the obb file on the sdcard. You have to have the write external store permission. Hope they recognize the issue and fix it now. The worst part is that google is refusing to accept it as a bug and fix the android OS, because apparently this is a bug that happens on all devices except their nexus devices, they are investigating the issue again here : This is why I'm saying unity did not fix the bug, because asking for the permission is not the solution, the user can deny it and the game will not run, this is why I have been doing as you are, asking for the permission myself and preventing the user from going forward into the game if he denies it, the result is that I've already received some 1 star reviews in the store because I require the permission, when I shouldn't even have to ask for it in the first place if android wasn't bugged.
The solution you posted is the same I've been using since I detected the bug, but this is not a proper solution, as none of us can actually fix the bug, because it's a bug in android, as posted here : Click to expand.I think there's a lot of misunderstanding going on in this thread.
0 kommentar(er)
