Search Issue Tracker
Won't Fix
Unknown (hidden) 2019.4.X, 2020.3.X, 2022.1.X, 2022.2.X
Votes
29
Found in
2019.4.39f1
2020.3.35f1
2022.1.3f1
2022.2.0a13
Issue ID
UUM-2303
Regression
No
[Android]"StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation" thrown in Google Play when APK is published
1. Open empty Unity project
2. Build Android APK
3. Upload APK to Google Play Developer console
Expected result - No API warnings are thrown
Actual result - API warning is thrown in Google Play developer console:
StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Ljava/lang/invoke/MethodHandles$Lookup;-><init>(Ljava/lang/Class;I)V
at android.os.StrictMode.lambda$static$1(StrictMode.java:428)
at android.os.-$$Lambda$StrictMode$lu9ekkHJ2HMz0jd3F8K8MnhenxQ.accept(Unknown Source:2)
at java.lang.Class.getDeclaredConstructorInternal(Native Method)
at java.lang.Class.getConstructor0(Class.java:2325)
at java.lang.Class.getDeclaredConstructor(Class.java:2166)
at bitter.jnibridge.JNIBridge$a.<init>(Unknown Source:25)
at bitter.jnibridge.JNIBridge.newInterfaceProxy(Unknown Source:8)
at com.unity3d.player.UnityPlayer.nativeRender(Native Method)
at com.unity3d.player.UnityPlayer.c(Unknown Source:0)
at com.unity3d.player.UnityPlayer$e$2.queueIdle(Unknown Source:72)
at android.os.MessageQueue.next(MessageQueue.java:395)
at android.os.Looper.loop(Looper.java:160)
at com.unity3d.player.UnityPlayer$e.run(Unknown Source:32)
Reproducible with - 2020.1.0a13, 2019.3.0b9, 2018.4.0f1
Note - See "edit" information if you don't want to create project from scratch to reproduce the issue
Comments (13)
-
PepoRuiz
Jul 05, 2020 17:50
I have the same error,
StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Ljava/lang/invoke/MethodHandles$Lookup;-><init>(Ljava/lang/Class;I)V
how can I resolve it? any solution??
Thanks!
-
alexTka
Apr 03, 2020 03:11
Also in 2019.2.12.
-
ciprianbiris
Feb 23, 2020 22:13
StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Ljava/lang/invoke/MethodHandles$Lookup;-><init>(Ljava/lang/Class;I)V
at android.os.StrictMode.lambda$static$1(StrictMode.java:428)
at android.os.-$$Lambda$StrictMode$lu9ekkHJ2HMz0jd3F8K8MnhenxQ.accept(Unknown Source:2)
at java.lang.Class.getDeclaredConstructorInternal(Native Method)
at java.lang.Class.getConstructor0(Class.java:2325)
at java.lang.Class.getDeclaredConstructor(Class.java:2166)
at bitter.jnibridge.JNIBridge$a.<init>(Unknown Source:25)
at bitter.jnibridge.JNIBridge.newInterfaceProxy(Unknown Source:8)
at com.unity3d.player.UnityPlayer.nativeRender(Native Method)
at com.unity3d.player.UnityPlayer.access$300(Unknown Source:0)
at com.unity3d.player.UnityPlayer$e$1.handleMessage(Unknown Source:95)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:193)
at com.unity3d.player.UnityPlayer$e.run(Unknown Source:20)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Issue not reproducible anymore. Google has removed MethodHandles.Lookup() method from their greylist.
Resolution Note (2022.1.X):
This is not a bug, but just a warning in Play store about potential issues in the future. Proper fix requires to use higher JDK version than 8. We don't plan to upgrade JDK in 2022.1.
Resolution Note (2020.3.X):
This is not a bug, but just a warning in Play store about potential issues in the future. Proper fix requires to use higher JDK version than 8. We don't plan to upgrade JDK in 2020LTS.
Resolution Note (2019.4.X):
This is not a bug, but just a warning in Play store about potential issues in the future. Proper fix requires to use higher JDK version than 8. We don't plan to upgrade JDK in 2019LTS.