Search Issue Tracker
Fixed in 2.0.1
Votes
0
Found in [Package]
2.0.0
Issue ID
1421863
Regression
Yes
[Mobile Notifications] Notification crashes application after updating app with an artifact containing extra values
How to reproduce:
1. Open project "MobileNotificationsException.zip"
2. Make sure the Mobile Notifications package is updated to 2.0.0
3. Change the platform to Android and Build an APK
4. Go to Plugins > Android and click on "Extra Values.androidlib" folder
5. In Inspector uncheck Android as included platform (if it was unchecked before, then check it)
6. Build the 2nd APK
7. Install 1st APK to the device
8. Open the app and press button to schedule notification that will appear after 60 seconds
9. Close the app and install 2nd apk with "adb install -r <path>" (the app does not need to be opened after that)
10. Wait for the notification to appear
Expected result: Notification appears with no errors
Actual result: Notification does not appear, logcat shows errors (some devices show window that the app has crashed). Error:
at android.content.res.ResourcesImpl.loadDrawableForCookie(ResourcesImpl.java:828)
at android.content.res.ResourcesImpl.loadDrawable(ResourcesImpl.java:673)
at android.content.res.Resources.loadDrawable(Resources.java:993)
at android.content.res.Resources.getDrawableForDensity(Resources.java:983)
Reproducible with: 2.0.0 (2019.4.38f1, 2020.3.33f1, 2021.3.2f1, 2022.1.0b16, 2022.2.0a12)
Not reproducible with: 1.4.3, 2.0.1 (2019.4.38f1, 2020.3.33f1, 2021.3.2f1, 2022.1.0b16, 2022.2.0a12)
Reproducible on these devices:
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00225, Qualcomm null (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
N/A, Huawei - (NOH-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G78
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
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
- Crash on PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
Resolution Note (fix version 2.0.1):
Fixed in: 2.0.1