Any updates @nick.carroll ?
1 Like
Seriously, an update on this matter is very much needed, our business depends on our App…
1 Like
Please do we have an update, on this issue? Thanks🙏
We have just lost 2 clients (with their users), because of this issue. Any update on this?
We are working on it - and also feel the pain, its blocking the newest version of BubbleGo on Android as well
Having the same issue with my app. It’s been live for 1+ year using BDK wrapper. My app is very dependant on photo sharing, although it is not considered a “core purpose” according to Google.
I had to update my app because of new API, 16ko pages and billing rules on Google Play. I have to make those changes before tomorrow (Oct. 31) otherwise I won’t be able to update my app anymore.
When I tried to upload a new version to Google Play Console, my app got rejected because of the READ_MEDIA_IMAGES/READ_MEDIA_VIDEO rule.
I tried searching for a way to include Android Photo Picker into my app, but couldn’t find how…
Is there any workaround possible?
If not this is a major issue for me and will probably need to move away from Bubble soon…
This is another week…AGAIN, and no update yet on this issue.
At this point I dont know what else to do.
My application doesn’t even have photo library access checked on in the device permissions of the bubble settings, but something in the manifest is telling google that it needs “Foreground service permissions”. As I understand this new google policy this application does require that permission because it calls an external API to update data in the database which then updates the current page data. In the Google Play Console when I click “Start Declaration”, I get the following message… “Your app uses the FOREGROUND_SERVICE_MEDIA_PLAYBACK permission“. I checked the bundle in the google play console and found in the permissions section both android.permission.FOREGROUND_SERVICE and android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK. Any update on getting this permission out of the manifest file would be greatly appreciated.
We are testing out a fix for this now. Will follow up in this thread
2 Likes
Hi everyone, good news - a fix is out for the read_media_images permissions issue. Please submit a new build and make sure to work through the different testing tracks (internal → closed → open) on the way to a new production release to ensure that an older version of the build isn’t still live in one of those testing tracks.
4 Likes
Woohoo Thanks @nick.carroll I will give it a shot and report back
I submitted a new build to Google Play yesterday, it was approved today and is working perfectly 
1 Like
Did you change anything from Bubble or Google Andorid Dev console side before submiting a new build ?
No changes in both sides. I made a new build, downloaded it, uploaded it to Google Play Console, submitted it for review, and that was it.
I submitted a new build to Google Playstore and it was approved. I can confirm that this issue has been resolved on my end. If anything else comes up on this issue, i will let us all know.
Thanks @nick.carroll and the bubble team on the hard work on this.
1 Like
Great to hear! Apologies for the delay but glad your builds are being approved now
2 Likes