Search Issue Tracker
Fixed
Fixed in 2021.3.33f1, 2022.3.13f1, 2023.1.20f1, 2023.2.5f1, 2023.3.0a11, 7000.0.0a1
Votes
11
Found in
2023.3.0a4
7000.0.0a1
Issue ID
UUM-48068
Regression
No
[Android] TargetAPI 34 crash on launch
*Steps to reproduce:*
# Open the attached 1361131_windowed-trunk project
# Build the application without changing settings
# Deploy to the application to target device
# Launch the application on device
# Observe immediate crash
- Alternatively deploy the attached APK to target device and repeat steps 4 & 5
*Expected results:* Application launches and information regarding the screen is visible alongside three rotating shapes.
*Actual results:* Crashes immediately
*Versions reproducible with:* 2023.3.0a4, 2021.3.33f1, 2022.3.14f1.
*Reproducible with:*
- Pixel 6, CPU: Google Tensor, GPU: Mali-G78, OS: 14 beta 3.1
*Not reproducible with:*
- Samsung Tablet A(8.0" 2019), CPU: Snapdragon 429, GPU: Adreno 504, OS: 11
- Xiaomi Redmi 9A, CPU: Helio G25, GPU: PowerVR GE8320, OS: 10
-
Thaoren
Oct 10, 2024 21:15
I'm porting a game made with 2019.4. Ideally we don't upgrade from 2019: is there an option for me manually configuring / removing the broadcast receiver registration code in the exported Android Project files?
-
unity_4C5DBF04B51DC8ECFA98
Sep 17, 2024 08:13
I've got this issue in 2020.3.16f1(LTS) and 2023.2.3f1 both version,
Now Updating it in 2023.2.5f1 as it says they have already removed the issue in this one. -
JVimes
Sep 11, 2024 16:14
Happens in blank project on 2022.3.12.
Android 14 is now required to upload to Google Play Console.
-
hohohocmc
Aug 13, 2024 14:06
2020.3.25f1 버젼 입니다.. 해결책을 알려주세요...
Caused by java.lang.RuntimeException: Unable to start activity ComponentInfo{/com.google.firebase.MessagingUnityPlayerActivity}: java.lang.SecurityException: com.ngelgames.tog: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3984)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4137)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:149)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:99)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2601)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:222)
at android.os.Looper.loop(Looper.java:314)
at android.app.ActivityThread.main(ActivityThread.java:8600)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:565)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1081) -
Msteva
Jul 23, 2024 11:24
same problem for unity 2022.3.11f1
have you found a solution? -
libin66
Jul 19, 2024 02:21
Regarding the solution for Unity2019.4.36, I decompiled the classes.jar & classes.dex in the Android installation directory, removed the "registerReceiver" related calls, and then replaced them back and put them in the installation directory.
-
haiyaojing
Jul 19, 2024 02:14
LIBIN66 is 666
-
libin66
Jul 16, 2024 07:06
What should I do about the 2019.4.36 version? I am not considering upgrading the Unity version for now.
-
IyadhSi
May 12, 2024 12:34
Running the game on a real Android 14 device works fine (Galaxy S22 Ultra), however the game crashes on startup on an Android Studio virtual device Android 14 (API 34)
-
IyadhSi
May 12, 2024 11:57
The issue still occurs in Unity 2022.328f1, Anyone got a fix so far?
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2023.3.0a11):
Crash was being caused on Android 14 devices on Development builds by missing EXPORTED/NOT_EXPORTED flag when registering broadcast receiver. Broadcast receiver was removed as it was unneeded and crash doesn't occur anymore.