INVALID_APP_ID after uninstalling / installing spotify app

[paicolman]

Hi,

I am developing an android app using spotify. I have registered the app in the dashboard, added both a debug key and a release key with an own keystore, all working fine. During tests I uninstalled spotify to check if the app warns the user that it needs to have spotify installed. After that I installed spotify again, and now I get the INVALID_APP_ID error. Any hints why this can happen? When I run ./gradlew signingReport, I get the two SHA's I have registered with Spotify, so I'm pretty lost here...

In case this helps and anyone in Spotify happens to take at least time to read this (seems not to be the case until now...):

-> SDK Version: 0.7 (Problem started in 0.6.3 though)
-> Created a new client ID in the dashboard to start with new credentials, but this did not help either

[gurpreetorem]

hi we all are facing same issue but support team not responding any more
they are disgusting

[joseandroidengineer]

@gurpreetorem Its okay to be upset, but lets keep things respectful. I'm sure the team is working on something of high priority. They probably looked at our issues and are working on it as we speak.

[paicolman]

@joseandroidengineer Agree, but a bit of feedback would be nice... (as in "you're doing it wrong" or "we know about this"...)

[mdelolmo]

Hi @paicolman

I get the two SHA's I have registered with Spotify, so I'm pretty lost here.

Why do you mean by this?

Before proceeding, let me give you a couple of generic hints that seem to be a common cause of confusion.

1. Make sure that, as mentioned in this comment, the signature is introduce in upper-case in developer-spotify.com
2. Unfortunately, due to an issue on our side, it's possible to register two apps with the same package-id/signature combination in developer.spotify.com. When this happens, the app authentication becomes unreliable. So please make sure that you only registered the package-id/signature once.

[paicolman]

Hi @mdelolmo

First of all: Thanks a lot for taking the time for my issue, really, really appreciate that!

I had two SHA signatures, one for development and one for the signed APK, and I also thought this could really be an issue, so I changed that, now I only habe one package name / SHA signature stored. What bugs me is, when spotify is not installed in my test phone, I can do the authorization and I do get a token, all perfect, but of course with no spotify installed I cannot play anything. With Spotify installed I get the "INVALID_APP_ID" thing.

I do have my SHA in caps. One thing though: Since I have been trying out stuff I have registered the same thing many times, I even created a new client ID with the same things, but deleted it again...

These are my settings in the dashboard:

[mdelolmo]

Hi @paicolman
Is that fingerprint the one for the upload key or the "publishing key"?
All these terms are very well explained here: https://developer.android.com/studio/publish/app-signing

[paicolman]

It was once the publishing key from google, but when I started having problems I changed it back to the development key you can generate within android studio... maybe that‘s bad?

[mdelolmo]

Yes @paicolman
That worked for another developer in
#185
I think it's worth a try

[paicolman]

@mdelolmo OK thanks! I'll try that out exactly as described and post my findings here...

[paicolman]

@mdelolmo Good news is: Yes, it works, I uploaded a new bundle and promoted it to beta on google play console, then downloaded is as a tester and it does work, thanks a lot!

The problem is: How can I continue debugging or do updates? If I build a new version with corrections in android studio, I will get the same APP_INVALID issue again, right? So how can I continue development while keeping the same signature as in Google play?

[mdelolmo]

Hi @paicolman
The order should not matter, but maybe I would start by creating a different package name for your debug builds and upload its key signature, so you'd have two entries in the developer console.

But, like you can see here you may have up to three entries, one for debug, one for play-store key and one for the upload key.

I understand this APK keys setup is a little bit confusing, so I would also encourage you to go through the following article from the official Android documentation. It will help you understand all types of keys and how to generate them:
https://developer.android.com/studio/publish/app-signing

[mdelolmo]

Related topics:
#185
#176