Check to make sure an app exists first about gradle-play-publisher HOT 4 CLOSED

Perhaps we should wrap that exception into our own exception like we did for invalid locales - #33

from gradle-play-publisher.

Is it possible to upload a new apk, whose package name is not yet registered at google play store ? In the androidpublisher sample it seems not to be part of. And when I have a look at the insert method of Google's API, the call is "POST https://www.googleapis.com/androidpublisher/v2/applications/packageName/edits" so this would explain, why I get a 404 on unknown package names.

Update of app works nicely. But before this is possible, one has to upload the apk manual once.

from gradle-play-publisher.

That is true. The first upload of an APK needs to be done through the web
interface.

janni2 [email protected] schrieb am Mo., 29. Juni 2015 15:07:

Is it possible to upload a new apk, whose package name is not yet
registered at google play store ? In the androidpublisher sample it seems
not to be part of. And when I have a look at the insert method of Google's
API, the call is "POST
https://www.googleapis.com/androidpublisher/v2/applications/packageName/edits"
so this would explain, why I get a 404 on unknown package names.

Update of app works nicely. But before this is possible, one has to upload
the apk manual once.

—
Reply to this email directly or view it on GitHub
#75 (comment)
.

from gradle-play-publisher.

@janni2 Thanks for confirming you are seeing the same exception.

from gradle-play-publisher.