# About upcoming full-screen intent permission change

**URL:** <https://devforum.zoom.us/t/about-upcoming-full-screen-intent-permission-change/108511>\
**Category:** Android\
**Created:** [April 23, 2024, 9:06pm UTC](https://devforum.zoom.us/t/about-upcoming-full-screen-intent-permission-change/108511 "2024-04-23T21:06:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuyang.chen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuyang.chen/32/47622_2.png) [@yuyang.chen](https://devforum.zoom.us/u/yuyang.chen)\
**Post date:** [April 23, 2024, 9:06pm UTC](https://devforum.zoom.us/t/about-upcoming-full-screen-intent-permission-change/108511/1 "2024-04-23T21:06:40Z")

</div>

**Description**  
Recently we are notified by Google that starting from May 31, 2024, `USE_FULL_SCREEN_INTENT` permission will no longer be granted by default if the app’s core functionality is not a high-priority use case of setting an alarm or receiving phone or video calls, which is the case for our app. Can see more here: [Behavior changes: Apps targeting Android 14 or higher &nbsp;|&nbsp; Android Developers](https://developer.android.com/about/versions/14/behavior-changes-14#secure-fsi).

We would like to know if this would cause issues on Zoom Meeting SDK integration, since the permission is used by Zoom, and we are worried that it would lead to crashes. Could Zoom provide any explanation or potential upcoming changes about this?

**Which Android Meeting SDK version?**  
5.17.10+

---

<div class="post-metadata">

**Author:** ![yuyang.chen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuyang.chen/32/47622_2.png) [@yuyang.chen](https://devforum.zoom.us/u/yuyang.chen)\
**Post date:** [May 20, 2024, 6:02pm UTC](https://devforum.zoom.us/t/about-upcoming-full-screen-intent-permission-change/108511/2 "2024-05-20T18:02:48Z")

</div>

Hi, I would like to follow up and see if you have any ideas about the potential impact of this upcoming policy change.

---

<div class="post-metadata">

**Author:** ![code\_defender123](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/code_defender123/32/60562_2.png) [@code\_defender123](https://devforum.zoom.us/u/code_defender123)\
**Post date:** [June 12, 2024, 10:33am UTC](https://devforum.zoom.us/t/about-upcoming-full-screen-intent-permission-change/108511/3 "2024-06-12T10:33:23Z")

</div>

@yuyang.chen , we have the same issue right now. Is there any official information from Zoom?

---

<div class="post-metadata">

**Author:** ![yuyang.chen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuyang.chen/32/47622_2.png) [@yuyang.chen](https://devforum.zoom.us/u/yuyang.chen)\
**Post date:** [June 14, 2024, 12:14am UTC](https://devforum.zoom.us/t/about-upcoming-full-screen-intent-permission-change/108511/4 "2024-06-14T00:14:08Z")

</div>

I haven’t heard back from Zoom as well. Wish we could get at least some information about this policy change.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [July 14, 2024, 10:14am UTC](https://devforum.zoom.us/t/about-upcoming-full-screen-intent-permission-change/108511/5 "2024-07-14T10:14:30Z")

</div>

Closed on July 14, 2024, 10:14am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
