-
Notifications
You must be signed in to change notification settings - Fork 11
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
About FOREGROUND_SERVICE #3273
Comments
That Re the use from Play Asset Delivery .. I can't actually see the documentation now that specifies that this was required, so let me check with the developer who'd put this together to find out the reason for its inclusion and whether it may be excluded now. But if it is still a requirement, then Google/Android should accept that this is required for using Play Asset Delivery and installing the asset packs etc. thanks |
Thanks for the quick answer. Indeed, I am not sure what requires that. I'll be waiting for your feedback! |
What extensions are you using? It is required by the android play core lib "to launch foreground extraction service for targetSdkVersion 28+" ( We also have a few extensions that use it for other purposes. |
I'm using these libraries: If I have to use it, what kind of message can I send to Google Play? |
Any news on that matter? |
The |
How can I present that information to Google so they validate the build? As you can see on the screenshot, they need a video and a description to validate the addition of that permission. |
FYI we've been looking at the Play Asset Delivery requirements, a lot of that has been updated and their documentation doesn't now talk about that permission.. although, it does still seem that it only works if we do have the So it might be you could omit that permission too? Worth just testing everything carefully (and on different versions of Android -> we're just starting to do this part too) to ensure it doesn't cause problems on particular older or newer devices. Would be nice if the Android documentation was clearer on all this :-( thanks |
What lines should I try to remove from the manifest? I have several lines mentionning "foreground":
|
I would just try removing the permissions if you don't plan to use the functionality. |
Just to be sure I understand well: I should try removing 1 & 2, right? |
I'll try to push a new version by removing 1 & 2. |
@ajwfrost https://developer.android.com/about/versions/14/changes/fgs-types-required?hl=pt-br |
Hi @bobaoapae - thanks for that; the link is about Foreground Services which we'd already reviewed, but we've not actually been able to find the details on what requirements there are with the different play asset delivery types. Do you have any reference for that i.e. something that says you don't need the play asset delivery library or service permissions if just using install-time? And it seems crazy that you would need to request Google's permission just to use their own play asset delivery functionality for fast-follow/on-demand..?! thanks |
If you check play asset delivery notification you will see that to use install time assets you just need the plug-in and configure assets folders on grade. And on the next section it's show the need of de library to use on demand and fast follow Check here: https://developer.android.com/guide/playcore/asset-delivery/integrate-java Now about the permissions, when you add dependency to the play asset delivery this automatically add the request for permission of foreground service etc, and those permission now on Android 14+ will need the form submission questing approval. I agree that this is not ideal, and also not very documented. But for use of play asset delivery library each user will need to use the form validation provided by Google. To Harman the unique alternative it's to just handle that to don't implement the library of using install time assets. Here I'm using my own ane to handle that, I use the assets resource on the application descriptor but I use my own ane to get those files, avoiding for complete the use of the play asset delivery and everything works like a charm without need of the form approval |
I use that code on my ANE to open assets packed using install-time, without any dependency |
@yvant were you able to push a new build ?
|
Yes, I was able to push the new build without said requirements. I can see some new ANR, but nothing critical: globally, my ANRs are a bit lower now. |
|
This one is not a problem for Google Play and is required for notifications I think. Just remove the other one. |
Recent updates within the AIR ecosystem now require that we upgrade the targetSDKVersion to 34.
Apparently, it comes with using android.permission.FOREGROUND_SERVICE, which wasn't require before.
With this new requirement, Google Play asks for a video and a description on how the app uses that requirement. Since I didn't know how to answer, I just said that it was a requirement because of the SDK upgrade + added a regular video of my game. The app update was rejected, here's an excerpt of the mail rejection:
What can I do to make it pass Google Play review? Is there a way to remove the FOREGROUND_SERVICE permission?
The text was updated successfully, but these errors were encountered: