OBB Fails to download from Google Play Store
We’re currently on the verge of sending out download links to our alpha testers and we’re distributing through the Google Play Store, and have been testing the process in office all week. We’ve opted to upload the .apk to the store, and the .obb file as an expansion file so that the download size is relatively small on the store. Unfortunately, it doesn’t work.
What’s supposed to happen as far as I can tell, is the user downloads the .apk from the store, then when they launch the game - it tries to find and/or download the .obb file. If you do this though, nothing actually happens. The progress bar goes nowhere and all we have on-screen is a message saying something along the lines of .XAPK failed verification - whatever that means. HOWEVER, if I close the app and wait a few minutes then launch it again, it opens up fine. Clearly the .obb is downloading but the game never launches once it finishes or shows any progress.
So what we’ve had to do, is check the box in Project Settings -> Android called ‘Disable verify OBB on first start/update’. This seems to make the .apk and the .obb download directly from the store in one go (which for us is currently 288mb and counting). We could live with that, but here comes problem #2:
For some reason when we download the game from the store, we cannot log into google play services. Works absolutely fine if we deploy directly to the device though. Going through LogCat, we found an error relating to a project number, but the project number does NOT match the one the project is actually linked to and when we click on the link, that project doesn’t even exist on the developer console. We’ve searched everywhere and can’t find a reference to this project number at all, so where is it coming from?
03-23 15:32:08.928 2065 28028 E SignInIntentService: Access Not Configured. Google Play Game Services API has not been used in project 608941808256 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/games/overview?project=608941808256 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
Preview 7 and Preview 8 are the only builds we’ve tried this on and both have failed. We can’t revert now and have no clue how to fix either issue. Not to give away our project ID, but ours actually starts with a ‘4’