# Android registering receivers must use RECEIVER\_EXPORTED / RECEIVER\_NOT\_EXPORTED **URL:** \ **Category:** Unity\ **Tags:** android\ **Created:** [January 23, 2025, 9:50am UTC](https://qa.fmod.com/t/android-registering-receivers-must-use-receiver-exported-receiver-not-exported/22534 "2025-01-23T09:50:38Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![nexusmind](https://avatars.discourse-cdn.com/v4/letter/n/d78d45/32.png) [@nexusmind](https://qa.fmod.com/u/nexusmind)\ **Post date:** [January 23, 2025, 9:50am UTC](https://qa.fmod.com/t/android-registering-receivers-must-use-receiver-exported-receiver-not-exported/22534/1 "2025-01-23T09:50:38Z")
Hello. As discussed at Google I/O 2023, registering receivers with intention using the “RECEIVER\_EXPORTED / RECEIVER\_NOT\_EXPORTED” flag was introduced as part of Android 13 and is now a requirement for apps running on Android 14 or higher (U+). > **[Behavior changes: Apps targeting Android 14 or higher  |  Android...](https://developer.android.com/about/versions/14/behavior-changes-14#runtime-receivers-exported)** > > Learn about changes in Android 14 that will affect apps when they target Android 14 or higher. We get some retrictions from google by using plugins where flags in registerReciever not used. After some investigations we found FMOD jar uses registerReciever without flag. Can you fix this? ---
**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\ **Post date:** [January 29, 2025, 2:43am UTC](https://qa.fmod.com/t/android-registering-receivers-must-use-receiver-exported-receiver-not-exported/22534/2 "2025-01-29T02:43:35Z")
I have passed this information onto the Dev team for implementation in a future release. Thank you for bringing this to our attention!