Closed PhilipSA closed 4 years ago
Nope, we can't do anything about that:
You can only use this API to make changes to an existing app (that has at least one APK uploaded); thus, you will have to upload at least one APK through the Play Console before you can use this API. Furthermore, you cannot use this API to change an app's state from "published" to "unpublished", or to fill out the legal consents required for publishing. To publish the app, you have to use the Play Console.
Though the fact that you got a notFound
exception instead of some authorization error should mean you're authed correctly.
Nope, we can't do anything about that:
You can only use this API to make changes to an existing app (that has at least one APK uploaded); thus, you will have to upload at least one APK through the Play Console before you can use this API. Furthermore, you cannot use this API to change an app's state from "published" to "unpublished", or to fill out the legal consents required for publishing. To publish the app, you have to use the Play Console.
Though the fact that you got a
notFound
exception instead of some authorization error should mean you're authed correctly.
If anyone else finds this and has the same issue; I got notFound
exception regardless if the .json had access or not. So do not rely on it
Maybe you can try publishing the app and checking that error message? It won't work of it's not on the play store, but it should still tell you that or fail with an authorization error.
For existing apps you can simply run the bootstrap gradle task to verify access. But if the app is not uploaded yet you will get 404.
There has to be a way to verify this before i upload the customers app. It is a real pain to try and convince the customer to fix any issues when the app is published.
Would be great if documentation could be added for the quickstart step.