Search Issue Tracker


Fixed in 2022.3.20f1



Found in


Issue ID




[Android] Player crashes with an error "Unable to instantiate fragment com.unity3d.player.a.c:" when minimizing and maximizing the player while a notification permission dialog is shown



How to reproduce:
1. Open the "IN_65631" project
2. In the Build Settings "Run Device" dropdown, select the desired device
3. Press Build And Run
4. On the Device in the Developer options enable "Don't keep activities"
5. Minime the Player and maximize it again without accepting or declining permission from the permission dialog window (repeat this step 2-3 times)

Expected result: Player doesn't crash
Actual result: Player crashes with an error (no Stack Trace) “java.lang.RuntimeException: Unable to start activity ComponentInfo\{com.DefaultCompany.AndroidFragmentCrash/com.unity3d.player.UnityPlayerActivity}“

Reproducible with: 2022.2.0a18, 2022.2.0a19, 2022.3.17f1
Not reproducible with: 2021.3.34f1, 2022.2.0a17, 2023.2.6f1, 2023.3.0b3
Fixed in: 2023.1.0a1

Testing environment: Windows 10 Pro, macOS Ventura 13.5.2 (M1)
Reproducible on: No other environment tested

Reproducible on these devices:
VLNQA00498 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 13
Xiaomi 11T (21081111RG), Android 13, CPU: NOT FOUND, GPU: Mali-G77 MC9

Not reproducible on these devices:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS

Couldn't test on these devices due to the notification permission access dialog window not being shown:
VLNQA00489, Htc 10 (HTC 10), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880

- Crash is not reproducible when the "Don't keep activities" option is disabled
- Not reproducible on iOS since it doesn't have the "Don't keep activities" option
- Not reproducible if notification access dialog isn't shown

First lines of an error:

java.lang.RuntimeException: Unable to start activity ComponentInfo\{com.DefaultCompany.AndroidFragmentCrash/com.unity3d.player.UnityPlayerActivity}:$InstantiationException: Unable to instantiate fragment com.unity3d.player.a.c: could not find Fragment constructor                 at                 at                 at

Comments (2)

  1. viveksaini75

    Jan 29, 2024 04:54

    I'm also facing the same issue

  2. RaventurnPatrick

    Jan 19, 2024 11:43

    Just to clarify: The crash also happens when the "Don't keep activities" options is disabled but it only happens when android decides to recreate an activity (this can happen when the user is using many apps at the same time or the device has a low amount of memory - however it can also happen in many other scenarios)

    It accounts for around 50% of all crashes in our live app on Google Play

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.