Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X
Votes
37
Found in
2021.3.31f1
2022.3.12f1
2023.1.17f1
2023.2.0b15
2023.3.0a11
Issue ID
UUM-55105
Regression
No
[Android] The Player crashes with a "JNI ERROR (app bug)" error when the global reference table gets overflowed by BillingClientStateListener
Reproduction steps:
1. Open the attached project "ReproProj" with Android Platform
2. Open the “PATHNAME” Scene
3. Install the Android LogCat package
4. Open the Android LogCat package (Window > Analysis > Android LogCat)
5. Open the Build Settings window (File > Build Settings)
6. Change the language of the Android device to Japanese
7. Build and Run on an Android device
8. Close Player
9. Change the language to English
10. Open the Player
11. Observe the Warning message in Android LogCat “Billing service disconnected.”
12. Let Player run for about 15 minutes
Expected result: "Billing service disconnected" occurs once and the Player does not crash and continues to run
Actual result: The error message "Billing service disconnected" keeps occurring and the Player crashes
Reproducible with: 4.9.4 (2023.1.17f1), 4.10.0 (2021.3.31f1, 2022.3.12f1, 2023.1.17f1, 2023.2.0b15, 2023.3.0a11)
Reproducible on:
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
Not reproducible on:
IOS devices (User reported)
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- 2021.3.31f1 did not crash, but "Billing service disconnected" keeps occurring
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment