Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal server error when running bootstrapListing and other tasks #1015

Open
safaorhan opened this issue Oct 11, 2021 · 6 comments
Open

Internal server error when running bootstrapListing and other tasks #1015

safaorhan opened this issue Oct 11, 2021 · 6 comments
Labels
bug Indicates an unexpected problem or unintended behavior feature:other Involves a feature that doesn't fit in existing categories

Comments

@safaorhan
Copy link

safaorhan commented Oct 11, 2021

Describe the bug

I have a developer account in which I have a private (managed google play) app.

I previously published a version of this app manually and verified users within the organization can download / install it.

I've been trying to publish another version over GPP plugin or to run other tasks like bootstrapListing but constantly getting a 500 internal server error for days.

Do you have any idea how to trouble-shoot this problem?

Does this plugin work with private apps too?

Do private apps require additional configuration on GPP's end?

Things I double-checked

  • Created a GCP project
  • Enabled publishing api for that project.
  • Linked the project to the Developer Console
  • Created a service account
  • Added this service account to Developer Console with all permissions checked.
  • Created a key to the service account and used it in the app/build.gradle as:
play {
   serviceAccountCredentials.set(file("service.json"))
}

Versions

  • Gradle Play Publisher: 3.6.0
  • Gradle Wrapper: 7.0.2
  • Android Gradle Plugin: 7.0.2

Tasks executed

bootstrapListing, bootstrapReleaseListing, publishApk, and many others.

Expected behavior

I should be able to publish an apk or run bootstrapListing task without an error.

Additional context

Execution failed for task ':app:bootstrapReleaseListing'.
> Multiple task action failures occurred:
> A failure occurred while executing com.github.triplet.gradle.play.tasks.Bootstrap$DetailsDownloader
> 500 Internal Server Error
POST https://androidpublisher.googleapis.com/androidpublisher/v3/applications/***/edits
{
"code": 500,
"errors": [
{
"domain": "global",
"message": "Internal error encountered.",
"reason": "backendError"
}
],
"message": "Internal error encountered.",
"status": "INTERNAL"
}
> A failure occurred while executing com.github.triplet.gradle.play.tasks.Bootstrap$ListingsDownloader
> 500 Internal Server Error
POST https://androidpublisher.googleapis.com/androidpublisher/v3/applications/***/edits
{
"code": 500,
"errors": [
{
"domain": "global",
"message": "Internal error encountered.",
"reason": "backendError"
}
],
"message": "Internal error encountered.",
"status": "INTERNAL"
}
> A failure occurred while executing com.github.triplet.gradle.play.tasks.Bootstrap$ReleaseNotesDownloader
> 500 Internal Server Error
POST https://androidpublisher.googleapis.com/androidpublisher/v3/applications/***/edits
{
"code": 500,
"errors": [
{
"domain": "global",
"message": "Internal error encountered.",
"reason": "backendError"
}
],
"message": "Internal error encountered.",
"status": "INTERNAL"
}
@safaorhan safaorhan added the bug Indicates an unexpected problem or unintended behavior label Oct 11, 2021
@SUPERCILEX
Copy link
Collaborator

Unfortunately, there's not much advice I can offer about 500s since they don't tell you what went wrong. One thing to check would be that your service account was created in the same GCP project that's linked to the play console (other people have gotten 500s on permission errors before). Otherwise, you'll probably have more luck contacting play support.

@safaorhan
Copy link
Author

safaorhan commented Oct 12, 2021

Yeah, I saw the other 500 error threads as well.

I also reached out to play support, created a stackoverflow question and asked around local dev communities.

One thing to check would be that your service account was created in the same GCP project that's linked to the play console (other people have gotten 500s on permission errors before)

We checked that but I'll let the owner check there once again.

@safaorhan
Copy link
Author

After talking to the Play Support I'm thinking that maybe I need to use Custom App Publishing API to publish apks for private apps.

Does, by any chance, this plugin support using Custom App Publishing API instead of the standard Publishing Api?

@SUPERCILEX
Copy link
Collaborator

Ohhhhh, yeah we don't support that as I'd never heard of it before. It looks cool though and I don't see why we couldn't support it, so is this something you'd be interested in?

@safaorhan
Copy link
Author

I'm not even sure about the scope of this API and not yet confirmed if the Publishing API can't be used to release private apps.

But if it's so, it would be great if I could use gradle-play-publisher to publish private apps too.

I will wait for the conversation with Play Support to finalize and then report back my findings here.

Perhaps I can open a separate issue to discuss what it needs to be done to integrate custom app publishing api to the plugin.

Thanks :)

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent
activity. It will be closed if no further activity occurs. Thank you for your
contributions.

@github-actions github-actions bot added the waiting-for-reply Indicates that an issue or pull request needs more information label Oct 23, 2021
@SUPERCILEX SUPERCILEX added the feature:other Involves a feature that doesn't fit in existing categories label Oct 29, 2021
@github-actions github-actions bot removed the waiting-for-reply Indicates that an issue or pull request needs more information label Oct 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior feature:other Involves a feature that doesn't fit in existing categories
Projects
None yet
Development

No branches or pull requests

2 participants