Search Issue Tracker
Fixed
Fixed in 2.4.3
Votes
0
Found in [Package]
2.4.2
Issue ID
MNB-94
Regression
No
[iOS] "Remote Notification Foreground Presentation Options" affect FCM behaviour even when Push Notifications are disabled
Steps to reproduce:
1. Create a new project
2. Install the Mobile Notifications package
3. Integrate Firebase Cloud Messaging (FCM)
4. Build and Run the iOS Player and send a push notification while the Player is in foreground
5. Observe the received notification
Expected result: Since “Enable Push Notifications” is disabled, Unity’s push notification settings do not affect FCM behaviour or the “Remote Notification Foreground Presentation Options” are defaulted to “None”
Actual result: The “Remote Notification Foreground Presentation Options” are defaulted to “All” and despite “Enable Push Notifications” being disabled, the value is still applied to all notifications
Reproducible with: 4.0.2 (2022.3.69f1)
Reproducible on: macOS 15.6 (by reporter), macOS 26.1
Not reproducible on: No other environments tested
Note: CQA reproduced the “Remote Notification Foreground Presentation Options” being defaulted to “All”. The FCM push notification behavior was not reproduced by CQA
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment