bitrise-steplib
Failed to commit edit, error: googleapi: Error 403: You must let us know whether your app uses any Foreground Service permissions., forbidden
Troubleshooting
- [x] I've searched discuss.bitrise.io for possible solutions.
- Which version of the step is effected? 3.75
- Is the issue reproducible with the latest version? YES
- Does the issue happen sporadically, or every time? EVERY TIME
- Is the issue reproducible locally by following our local debug guide? NOT APPLICABLE
Useful information
Issue description
We updated the radar library in our project. implementation 'io.radar:sdk:3.9.8'
That library now:
Adds FOREGROUND_SERVICE_LOCATION permission to Android manifest.
The bitrise step to deploy the build to the Play Store now fails with:
Failed to commit edit, error: googleapi: Error 403: You must let us know whether your app uses any Foreground Service permissions., forbidden
If I manually add that permission to my manifest, it then gives two of these errors instead of one.
We've rolled back the library version so that we can deploy, but need guidance on how we can prevent this step from failing when we do update the library.
Bitrise info
- Build URL: https://app.bitrise.io/build/c8e38a69-dcc1-493f-8a41-e191c9000714
- Bitrise Support enabled: YES / NO
- Log:
Using mapping file from: /bitrise/deploy/app-mapping-20240404223738.txt Using app from: /bitrise/deploy/app-release.aab Configuration read successfully Authenticating Authenticated client created Create new edit editID: 15281108605623137801 Edit insert created Available tracks on Google Play: - production - beta - alpha - internal Tracks listed Upload apks or app bundles Uploading /bitrise/deploy/app-release.aab 1/1 Uploaded app bundle version: 370 uploaded mapping file for apk version: 370 Done uploading of 1 apps New version codes to upload: 370 Applications uploaded Update track Release version codes are: [370] Update listing started Update listing finished internal track will be updated. updated track: internal Track updated Committing edit Failed to commit edit, error: googleapi: Error 403: You must let us know whether your app uses any Foreground Service permissions., forbidden | | +---+---------------------------------------------------------------+----------+ | x | Google Play Deploy (Failed) | 1.2 min | +---+---------------------------------------------------------------+----------+ | Issue tracker: https://github.com/bitrise-io/steps-google-play-deploy/issues | | Source: https://github.com/bitrise-io/steps-google-play-deploy | +---+---------------------------------------------------------------+----------+
Steps to reproduce
Add radar, try to submit a build to the store.
Caveat: The issue might be with Radar's SDK, I have an issue open with them too.
You may try uploading your app manually on the UI of Google Play console and try to resolve any warnings there first. After that automated deploy could be continued.
Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.
To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.
The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".
If no comment left within 21 days, this issue will be closed.
Hi @jt-gilkeson @tsakmalis , have you guys found any solution for this?
We had to upload manually. So basically I had to change our bitrise steps to create build on bitrise and then manually upload it to the play store, which then prompted for an explanation about the foreground service, which we were able to then submit a response bout how the foreground service was being used, then publish it. Then after that go back and change the bitrise flow to re-enable uploading to the play store for future builds. Kind of a pain, but fortunately you only have to do it once.
Just a pro tip for speeding up the work.
- Create a new workflow using on that fails and remove sep with distribution.
- Add step with Deploy to Bitrise.io so you have the apk build After uploading apk manually just remove newly created workflow
Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.
To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.
The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".
If no comment left within 21 days, this issue will be closed.
I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.