Android shipping build crash - Google Play Services related
Here is the problem: My Shipping build is crashing at startup. It was working fine before and the Development build works fine. The thing that crashes the app is using the Google Play services, which again worked fine before.
So here is the full story. I was copying the project to another machine and after opening it again on the original PC the Build folder was missing. I have no idea how that happend, but on the phone - that was used as a usb drive the Build folder does exist, however it's empty...
So basically the Build folder got corrupted.
The app was already in Alpha testing, signed with keystore, working Google Play achievements. Everything was working like a charm.
So I had to make the platform files writeable again, I had to add the icons again. I did recover my keystore file (from Intermediate folder) and put it again in the Build folder. And the new builds are simply crashing on startup. And if I try to upload my new .apk it says that my app is signed with another key:
But I did not have any other keystore file, so if I did copy it back into the Build folder, than what the hell is wrong with it, or sth else...
Once I turn the Google Play services off everything works fine, including AdMob.
I did also try to change the package name (I did change the name of the company a bit) I have generated a new keystore, I have uploaded the "new" app to the play console, I have connected the new app to the service and after installing it from Google Play it crashed just like the old one...
I have sent the crash report and this is what I got in the Play Developer console:
At this point I am basically out of ideas. I have tried to package the app with the keystore from backup, and I have tried to package the game under new package name with new keystore, and both are crashing once they try to use Google Play services. To be honest I do not get it why any of these ways are failing. One is using the same keystore file as before, the other one is having different package name and is using it's own keystore...
asked Apr 20 '15 at 11:29 AM in Packaging & Deployment
I was just going to make that test build that crashes on the phone at startup and this time the build failed. As I did solve the problem and there is clearly sth wrong with that old project (the folder was missing) I guess there is no point in investigating it any further.
answered Apr 26 '15 at 08:19 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here