Not processing

Target Platforms Mobile
1

Hi,

I’ve been trying to upload an expansion file to Play for a few days now with no luck, it always seems to get stuck in ‘Processing’

In my last test I left it over night but despite this it still didn’t get past this window, the apk uploads just fine. Even if I close the window and check there is no expansion uploaded.

Any thoughts on what could be causing this?

Edit: possible solution below

2

Ok think, I was making this more confusing than it had to be, make sure your device has been restarted and you have everything set to the correct directory.

Thanks all!

3

I’m having the same issue
Not sure what’s going on, it’s my first time exporting for android…

4

Make sure you sign the application with a proper key. If it’s signed with a debug key google sometimes silently fails the upload.

5

Hi,
I can’t see anywhere in unity where my key could have been set to debug key, I tried to create a new keystore but now when I upload the APK it says that I can’t because:

"Upload failed
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
SHA1: E2:E4:0D:5A:8C:33:64:2A:22:25:B4:33:C0:FC:01:44:96:8E:9C:2E
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
SHA1: 46:88:F1:75:62:87:A0:51:06:73:FF:06:39:1B:smile:3:3B:AF:F9:86:8D"

I imagine it’s because I signed it with a new Keystore.
How can I delete the previous apk sent? (if it’s possible).

Here is how I set up the Other Settings in player prefs:

  • Bundle identifier: com.CompanyName.APKName (that’s an example obviously :wink: )
  • Bundle Version: 1.0
  • Bundle Version Code: 1
  • Minimum API: (lowest) 2.0.1
  • Device filter: Armv7 only
  • Install Location: Prefer Extern
  • Graphics Level: OpenGL ES 2.0
  • Internet: Auto
  • Write Access: Internal only
  • API: .NET 2.0 subs

The product name is different than the APK name.

My files are named:

  • APK: APKName
  • Expansion file: main.1.com.CompanyName.APKName

In the build settings, nothing is changed (Development Build is still False).

I’m not sure what I’m doing wrong. I read too that if the name of the expansion file isn’t correct google silently fails the upload too. Does the Product name and the APK name has to be the same?

Thanks for the help

Boris

6

You need to publish a new app (change the package name) if you change the key signature.

7

I’ve completely restarted fresh and it’s still not working (new app in google play, new package name, new keystore). I can’t find anything online about this, it’s really frustrating.

EDIT: Do I need to do something specific with the keystore to kind of link it with google play or something?

8

Ok I did it!!!

I had to create another version of my app with a higher version number. Then I went to the old console, as my app wasn’t accessible through the old console I had to upload again my first APK by clicking on upload apk. Once uploaded the old console shows an error saying that there is already an app with that package name. After closing the error message the app is accessible through the old console and therefore from there I was able to upload my version 2 (the new one) APK + main OBB. After that, from the old console, I deactivated the old version and deleted it. I went back to the new console design and this is it !!!

They don’t make it easy…