Search Issue Tracker
Fixed in 1.4.0
Votes
0
Found in [Package]
1.4.0
Issue ID
1326125
Regression
No
[Mobile Notifications] Notifications are not received after device restart
To reproduce:
1. Open notification sample project
2. Queue a Notification after restart
3. Restart your devices and wait for ~60 seconds for notification to arrive
Expected: notification arrives after device restart
Actual: notification does not arrive
Reproduced in: 2021.1.1f1
Reproduced in package: 1.3.2, 1.4.0
Reproduced on devices:
----------, Google Pixel 2 XL (Pixel 2 XL), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 11, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00011, Xiaomi Mi 5s (MI 5s), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
----------, Xiaomi Mi A2 (Mi A2), Android 10, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00010, Samsung Galaxy S8 (SM-G950U), Android 7.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Not reproduced with devices:
VLNQA00230, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Add comment
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
Resolution Note (fix version 1.4.0):
Notifications do get delivered, just time was a bit too small, hence notification times out. Increasing time in test does solve it.