We have recently converted our app to using a mounted obb file. In the past the obb was just a zip file and we unzipped it for use. Since the obb is large (300 MB to 1.2 GB depending on app version) we decided to create it using using JOBB and mount it. This is working very well on most platforms, but there are a few where the obb can't be mounted. I have seen many reports of this problem with an encrypted obb, but ours is not.
The obb was created on a Mac using the command: jobb -d LiteOBB -o main.400.com.simulationcurriculum.skysafari4.obb -pn com.simulationcurriculum.skysafari4 -pv 400 This obb is then uploaded to Google Play to be downloaded by the customer as part of the APK Expansion mechanism One the majority of platforms this has worked well for us. The obb can be successfully mounted and accessed. However, on a few, we always get the error ERROR_COULD_NOT_MOUNT coming back from the OnObbStateChangeListener. Platforms with the problem are: Droid Maxx running Android 4.4.x (works fine on 4.1) Asus Memo 7 running Android 4.2 Some other devices running custom KitKat ROMs With the custom ROMs, the error the user sees is generally "Unfortunately, Package Acces helper has stopped". I'm not 100% sure it is the same problem, but it is an issue mounting the obb I've been pulling my hair out over this. Customers are yelling at us. Why can't the obbs be mounted on the above platforms? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
