Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.4.0
Issue ID
1320301
Regression
No
[Android] [Notifications] ”Notification not found” error after the device is unlocked
How to reproduce:
1. Open the attached project
2. Build & run project on mobile device
3. Lock the device
4. Unlock the device
5. Observe Logs section
Reproducible: 2019.4.21f1, 2021.1.0b9, 2021.2.0a8
Expected result: no issues
Actual result: ”Notification not found” error is shown
Reporoducible on:
Google Pixel 4, CPU: Snapdragon 855 (SM8150), GPU: Adreno (TM) 640, Android: 10
VLNQA00287, Motorola moto g(7) power, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506, Android: 9
VLNQA00340, Samsung Galaxy Note20 Ultra 5G (SM-N986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00269, Samsung Galaxy S10e (SM-G970F), Android 10, CPU: Exynos 9 9820, GPU: Mali-G76
VLNQA00336, Huawei Y6p, CPU: MediaTek MT6762R, GPU: PowerVR Rogue GE8320, Android: 10
VLNQA00111, Samsung Galaxy J5(2016) (SM-J510FN), Android 7.1.1, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
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
- Reflection problems when unbaked Reflection Probes are present
- Light Explorer columns sorting arrow is too small
- Context menu actions (Collapse All, Expand All, Enable All, Disable All, Remove All, Reset All) do nothing in Volume component
- [Android] Audio volume decreases when returning to the app during screen recording
- Graphical issues are caused by GPU Occlusion Culling when using Amplify Shaders
Resolution Note:
The error is presented, because the notification used to launch the app is not found.
The idea there is:
- launch the app
- schedule the notification (one of the buttons)
- send app to background
- press on notification to show the app again
After these steps the app is launched via notification and information is retrieved. You can lock and unlock the device - the notification info will be shown.