-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Google restricts the use of the USE_FULL_SCREEN_INTENT permission. #222
Comments
Hi @pyjserv, Regarding your issue with the USE_FULL_SCREEN_INTENT permission:
If there are specific changes needed in the alarm plugin to support these requirements better, please let me know, and I’ll be happy to assist. Best regards, |
Hi, @gdelataillade Thank you for your reply. As mentioned in the Google document you provided, starting from Android 14, only apps with alarm and call functionalities will have the USE_FULL_SCREEN_INTENT permission enabled by default. I believe I have set the app category to alarm (as shown in the picture), but the review was still rejected. |
Hi @pyjserv, When submitting your app for review, include a detailed note explaining why the full-screen intent is essential for your alarm functionality. Clearly state that the permission is necessary for delivering timely and critical alarm notifications, aligning with user expectations and the app’s primary purpose. You can include this note in the “App Content” section under the “Privacy Policy” or “App Permissions Declaration” fields during the submission process. Let me know if it helps. |
Unfortunately, Google informed me that the review did not pass. Due to my lack of experience and English not being my first language, I hope you or anyone can provide some advice and assistance. This is my third or fourth review rejection, and I am very confused and anxious. In addition to appealing the USE_FULL_SCREEN_INTENT permission review, I have made other efforts:
However, there are several parts of Google's response (full text here) that I am unsure if I understood correctly, so I sought help from Google with the following three questions:
Is there really a way to request permission from the user to use USE_FULL_SCREEN_INTENT now? Whether it's an Android native method or a Flutter plugin, can you provide some clues?
Does this mean I need to explicitly tell users in the full description of my app’s store listing that the USE_FULL_SCREEN_INTENT permission will be used?
I cannot understand “the alarm working outside the app with interactive controls or a full-screen alarm display,” do you have any practical examples that could help understand? Does this mean only certain types of apps, such as those showing a large clock when opened, can be recognized as alarms? I don’t understand what key content was missing in my previous demo video. This is Google's response (full text here). After reading it, I am still very confused. I don’t know if I currently have no possibility of applying for the USE_FULL_SCREEN_INTENT permission, or if I can pass the review as long as I complete the required parts. Or did I misunderstand or misuse something? |
I'm in the same situation. App rejected by Google. Exactly the same thing.
|
Hi @desenvolvedor-apanheidoexcel You're right, it's declared in alarm library. You can add Be sure the attribute exists in the root tag of your app's manifest: Then add |
What are the consequences of not using this permission? In practice... can anyone tell me? I tested it (node=remove) on my app and everything worked normally. At first. |
Hi @desenvolvedor-apanheidoexcel
You can watch my demonstration video showing the screen automatically turning on while ringing: https://www.youtube.com/shorts/IgffqLThNKA. In my case, if I remove the declaration of the USE_FULL_SCREEN_INTENT permission, the screen will not automatically turn on while ringing.
I did this and officially released the new version of the app. However, without the USE_FULL_SCREEN_INTENT permission, the user experience will be reduced. |
Your solution really worked by removing the USE_FULL_SCREEN_INTENT permission with code above in Manifest:
The version was approved and published in the play store. |
Hi @gdelataillade, Although my appeal failed, I continue to observe how others are doing it. I found that most Pomodoro apps also do not have the USE_FULL_SCREEN_INTENT permission. However, some apps wake up the screen when the reminder notification is activated (only waking up the locked screen, and the screen remains locked, unlike apps with the USE_FULL_SCREEN_INTENT permission, which directly display on the locked screen). Could you please add this feature to the new version of the alarm? |
Hi @pyjserv Yes I could add a wake lock when alarm starts ringing to make sure the screen is on. But I need to set a wake lock duration and I'm wondering how long it should be. For long durations the battery can drain but for short duration the user could miss the wake lock. What do you think ? |
My personal experience is that 15 to 30 seconds is enough. However, can this become a setting value in AlarmSettings? |
Hi, @gdelataillade
I'm not sure whether I should post this in issues or discussions. Here's the situation: I developed a simple calendar app with a countdown timer and published it on the Play Store: https://play.google.com/store/apps/details?id=com.claberi.consilia
Recently, due to Google's restriction on the USE_FULL_SCREEN_INTENT permission, my app failed to pass review and I couldn't publish updates. I have appealed several times without success.
Since simply removing the declaration from my app still resulted in denial by Google, I had to download and manually remove the USE_FULL_SCREEN_INTENT declaration from the alarm plugin to pass the review.
I would like to ask if there is currently any way to request users to grant the USE_FULL_SCREEN_INTENT permission?
The text was updated successfully, but these errors were encountered: