This worked great when I started fresh with a new project, both in Unity and on Google Play.
However, when I try to implement it in my existing project I get an error:
This happens after I click the download button in the example.
Any way to narrow down what setting I need change to get this working?
The only hint I have is that I am using several prime31 plugins along with the Google Play OBB Downloader plugin. They both seem to want to modify the AndroidManifest.xml file, along with styles.xml, strings.xml, and main.xml. I have done my best to merge these manually, however I’m not really sure what some of it is doing.
I’m having a similar problem. Have you made any progress on this? We’ve never used the OBB downloader before and I’m not sure what settings could cause this problem.
“Download failed because resources could not be found” is due to propagation on Google’s servers. You just need to wait a little longer before testing.
the downloaderscene trys to start the download … after a few seconds it says that the download has finished
but he it did not download anything … is this supposed to happen since the App is not published yet or is there an error?
Also having this problem. Could this happen when the LVL is wrong or what could cause this? It can’t be because I tried too soon after uploading the apk/obb, because that was 24 hours ago.
I just split the APK and upload the APK and the expansion file to Google Play. I didn’t add the OOB downloader to my project but everything still works. No customer has complained. Not sure the OOB downloader is needed for Google Play.
I think it’s only needed in a minority of cases where the OBB file is not automatically downloaded (apparently some devices will not download the expansion at the same time). I want to make sure that in these cases the customer will be able to automatically download the OBB, but I’m having trouble with that.
I will just ask here instead of creating a new thread.
Is anyone else having problem RESUSING an OBB package?
I bump bundle version and leave bundle version code but launching new build with the old obb on the proper place still gives “add level to build settings”.
Only way for me to getting it work properly is to bump OBB version as well - any ideas?
I’ve always had to use the exact OBB that came with the APK every time I made any changes, otherwise always had that error. This was even in cases where the OBB’s were the same version code, name, and exact file size. I’m currently waiting a couple hours to make sure google has correctly set my OBB to the newer one in order to do a quick test. Not sure if there are any workarounds for faster testing when you need to download it from google.
All right, thanks straafe.
Will put in a bug report - see what happens…
Just got a one star rating saying “each update uses up 300MB more of sd card each time”… aaaarg sometimes I wish I could reach in to the screen and grab the person …
In Unity 4.3 the plugin will crash the app/device any time it tries to do the download. I had to (re)install the 4.2.2 Unity to keep working on a project.
I upload the apk and OBB to Google Play for about two days, but when I run the apk, I get “Download failed because the resources could not be found”, how to solve this?