Search Issue Tracker
Fixed in 1.0.3-preview.4
Votes
0
Found in [Package]
1.0.3-preview.4
Issue ID
1173038
Regression
No
[Mobile Notifications] [Android] Tapping a notification doesn't do anything if non-default activity is used
Steps to reproduce:
1. Build and Run the user-attached project
2. Suspend the app (put it into the background)
3. Wait 10 seconds. A local notification appears.
4. Tap the notification.
Expected result: the app activates.
Actual result: nothing happens.
Reproduced in: 2017.4.30f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Notes: Could not build on iOS
Tested on:
VLNQA00010, Samsung Galaxy S8 (SM-G950U), Android 7.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00257, Sony Xperia XZ Premium (G8141), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00272, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment