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.
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 |
+---+---------------------------------------------------------------+----------+
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.
I saw that I could open an issue on github for this step, so I did that too.
Caveat: The issue might be with Radar’s SDK, I have an issue open with them too.
Also I was reading about another library that did this and the comment was made that:
From what I can read in Google documentation here there should be a new section in the Play console where I can fill out additional details for Foregrounds services if I’m targeting Android 14.
However to me it seems like an chicken and the egg situation where I can’t even submit my application to let Play console know that I’m targeting that Android version, because the submission process is blocking me, so that new section in the Play console isn’t visible.