Search Issue Tracker
Fixed
Fixed in 2.2.0
Votes
0
Found in [Package]
2.1.1
2.2.0
Issue ID
MNB-36
Regression
No
[MobileNotifications][Android][GameActivity] Scheduled notification doesn't arrive after app is killed when Application Entry Point is set to Game Activity
Steps to reproduce:
- Open the Main project
- Go to File > Build Settings and select Android Platform
- Go to Edit > Project Settings > Player > Other Settings
- Set Application Entry Point to Game Activity
- Build and Run on a device
- In the application press "[5s] Empty Notification + body"
- Kill the app
Expected: Notification arrives after 5 seconds
Actual: Notification doesn't arrive
Reproducible with: 2.1.1(2023.1.0b6, 2023.2.0a4)
Could not test with: 2020.3.45f1, 2021.3.20f1, 2022.2.9f1 (Game Activity is not available)
Tested and reproduced on devices:
- VLNQA00467 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 12
- VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 13
Notes:
- If the app is not killed, but only put in the background notification arrives
- Sometimes after the app is killed application crashes
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment