Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Question Crash on launch (even a sample project) - Android 4.4.4 - Unity 2019.4

Discussion in 'Editor & General Support' started by erpresi, May 11, 2021.

  1. erpresi

    erpresi

    Joined:
    Oct 28, 2014
    Posts:
    7
    Hello I have tried to upgrade my project from Unity 2019.2 to Unity 2019.4 (LTS) and it crashes for some devices (Galaxy Tab E for example) runing Android 4.4.4 and/or Android 5. The error is just on the launch and the logs just say this (this is the output for a sample project such the one that appears by default wwhen you create a new project but the crash is exactly the same in my project):

    D/dalvikvm: Trying to load lib /data/app-lib/com.DefaultCompany.TestProject-1/libmain.so 0x41dd4740
    05-11 15:38:41.726 17664-17664/? D/dalvikvm: Added shared lib /data/app-lib/com.DefaultCompany.TestProject-1/libmain.so 0x41dd4740
    05-11 15:38:41.756 17664-17664/? I/dalvikvm: Failed resolving Lcom/unity3d/player/j$a; interface 118 'Landroid/view/PixelCopy$OnPixelCopyFinishedListener;'
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: Link of class 'Lcom/unity3d/player/j$a;' failed
    05-11 15:38:41.756 17664-17664/? I/dalvikvm: Failed resolving Lcom/unity3d/player/j$a; interface 118 'Landroid/view/PixelCopy$OnPixelCopyFinishedListener;'
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: Link of class 'Lcom/unity3d/player/j$a;' failed
    05-11 15:38:41.756 17664-17664/? I/dalvikvm: Failed resolving Lcom/unity3d/player/j$a; interface 118 'Landroid/view/PixelCopy$OnPixelCopyFinishedListener;'
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: Link of class 'Lcom/unity3d/player/j$a;' failed
    05-11 15:38:41.756 17664-17664/? E/dalvikvm: Could not find class 'com.unity3d.player.j$a', referenced from method com.unity3d.player.j.a
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: VFY: unable to resolve new-instance 242 (Lcom/unity3d/player/j$a;) in Lcom/unity3d/player/j;
    05-11 15:38:41.756 17664-17664/? D/dalvikvm: VFY: replacing opcode 0x22 at 0x0012
    05-11 15:38:41.756 17664-17664/? I/dalvikvm: Failed resolving Lcom/unity3d/player/j$a; interface 118 'Landroid/view/PixelCopy$OnPixelCopyFinishedListener;'
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: Link of class 'Lcom/unity3d/player/j$a;' failed
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: VFY: Ljava/lang/Object; is not instance of Landroid/view/View;
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: VFY: bad arg 1 (into Landroid/view/View;)
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: VFY: rejecting call to Landroid/view/ViewGroup;.addView (Landroid/view/View;)V
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: VFY: rejecting opcode 0x6e at 0x0004
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: VFY: rejected Lcom/unity3d/player/j;.a (Landroid/view/ViewGroup;)V
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: Verifier rejected class Lcom/unity3d/player/j;
    05-11 15:38:41.756 17664-17664/? D/AndroidRuntime: Shutting down VM
    05-11 15:38:41.756 17664-17664/? W/dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x417ebbc0)
    05-11 15:38:41.756 17664-17664/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.DefaultCompany.TestProject, PID: 17664
    java.lang.Error: FATAL EXCEPTION [main]
    Unity version : 2019.4.26f1
    Device model : samsung SM-T560
    Device fingerprint: samsung/gtelwifixx/gtelwifi:4.4.4/KTU84P/T560XXU0APL1:user/release-keys

    Caused by: java.lang.VerifyError: com/unity3d/player/j
    at com.unity3d.player.UnityPlayer.<init>(Unknown Source)
    at com.unity3d.player.UnityPlayerActivity.onCreate(UnityPlayerActivity.java:41)
    at android.app.Activity.performCreate(Activity.java:5447)
    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1094)
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2393)
    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2493)
    at android.app.ActivityThread.access$800(ActivityThread.java:166)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1283)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:136)
    at android.app.ActivityThread.main(ActivityThread.java:5590)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:515)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)
    at dalvik.system.NativeStart.main(Native Method)


    Super thanks!
     
  2. Seanm07

    Seanm07

    Joined:
    Mar 18, 2014
    Posts:
    12
    I'm having the exact same crash on the Samsung Tab 4 (SM-T230) and Tab E (SM-T375) after updating from Unity 2019.4.22f1 to Unity 2019.4.26f1 looks like the latest update broke something for either older android versions or just older devices.

    Code (CSharp):
    1. 05-20 12:20:47.485: I/dalvikvm(6134): Failed resolving Lcom/unity3d/player/j$a; interface 220 'Landroid/view/PixelCopy$OnPixelCopyFinishedListener;'
    2. 05-20 12:20:47.485: W/dalvikvm(6134): Link of class 'Lcom/unity3d/player/j$a;' failed
    3. 05-20 12:20:47.485: I/dalvikvm(6134): Failed resolving Lcom/unity3d/player/j$a; interface 220 'Landroid/view/PixelCopy$OnPixelCopyFinishedListener;'
    4. 05-20 12:20:47.485: W/dalvikvm(6134): Link of class 'Lcom/unity3d/player/j$a;' failed
    5. 05-20 12:20:47.485: I/dalvikvm(6134): Failed resolving Lcom/unity3d/player/j$a; interface 220 'Landroid/view/PixelCopy$OnPixelCopyFinishedListener;'
    6. 05-20 12:20:47.485: W/dalvikvm(6134): Link of class 'Lcom/unity3d/player/j$a;' failed
    7. 05-20 12:20:47.485: E/dalvikvm(6134): Could not find class 'com.unity3d.player.j$a', referenced from method com.unity3d.player.j.a
    8. 05-20 12:20:47.485: W/dalvikvm(6134): VFY: unable to resolve new-instance 3204 (Lcom/unity3d/player/j$a;) in Lcom/unity3d/player/j;
    9. 05-20 12:20:47.485: D/dalvikvm(6134): VFY: replacing opcode 0x22 at 0x0012
    10. 05-20 12:20:47.485: I/dalvikvm(6134): Failed resolving Lcom/unity3d/player/j$a; interface 220 'Landroid/view/PixelCopy$OnPixelCopyFinishedListener;'
    11. 05-20 12:20:47.485: W/dalvikvm(6134): Link of class 'Lcom/unity3d/player/j$a;' failed
    12. 05-20 12:20:47.485: W/dalvikvm(6134): VFY: Ljava/lang/Object; is not instance of Landroid/view/View;
    13. 05-20 12:20:47.485: W/dalvikvm(6134): VFY: bad arg 1 (into Landroid/view/View;)
    14. 05-20 12:20:47.485: W/dalvikvm(6134): VFY:  rejecting call to Landroid/view/ViewGroup;.addView (Landroid/view/View;)V
    15. 05-20 12:20:47.485: W/dalvikvm(6134): VFY:  rejecting opcode 0x6e at 0x0004
    16. 05-20 12:20:47.485: W/dalvikvm(6134): VFY:  rejected Lcom/unity3d/player/j;.a (Landroid/view/ViewGroup;)V
    17. 05-20 12:20:47.485: W/dalvikvm(6134): Verifier rejected class Lcom/unity3d/player/j;
    18. 05-20 12:20:47.485: D/AndroidRuntime(6134): Shutting down VM
    19. 05-20 12:20:47.485: W/dalvikvm(6134): threadid=1: thread exiting with uncaught exception (group=0x41b09c08)
    20. 05-20 12:20:51.499: E/AndroidRuntime(6134): FATAL EXCEPTION: main
    21. 05-20 12:20:51.499: E/AndroidRuntime(6134): Process: com.pickle.FlyingCarShooting, PID: 6134
    22. 05-20 12:20:51.499: E/AndroidRuntime(6134): java.lang.Error: FATAL EXCEPTION [main]
    23. 05-20 12:20:51.499: E/AndroidRuntime(6134): Unity version     : 2019.4.26f1
    24. 05-20 12:20:51.499: E/AndroidRuntime(6134): Device model      : samsung SM-T230
    25. 05-20 12:20:51.499: E/AndroidRuntime(6134): Device fingerprint: samsung/degaswifixx/degaswifi:4.4.2/KOT49H/T230XXU0AOD2:user/release-keys
    26. 05-20 12:20:51.499: E/AndroidRuntime(6134): Caused by: java.lang.VerifyError: com/unity3d/player/j
    27. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at com.unity3d.player.UnityPlayer.<init>(Unknown Source)
    28. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at com.unity3d.player.UnityPlayerActivity.onCreate(UnityPlayerActivity.java:41)
    29. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at com.google.firebase.MessagingUnityPlayerActivity.onCreate(MessagingUnityPlayerActivity.java:91)
    30. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.app.Activity.performCreate(Activity.java:5451)
    31. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1093)
    32. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2377)
    33. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2471)
    34. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.app.ActivityThread.access$900(ActivityThread.java:175)
    35. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1308)
    36. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.os.Handler.dispatchMessage(Handler.java:102)
    37. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.os.Looper.loop(Looper.java:146)
    38. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at android.app.ActivityThread.main(ActivityThread.java:5602)
    39. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at java.lang.reflect.Method.invokeNative(Native Method)
    40. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at java.lang.reflect.Method.invoke(Method.java:515)
    41. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1283)
    42. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1099)
    43. 05-20 12:20:51.499: E/AndroidRuntime(6134):     at dalvik.system.NativeStart.main(Native Method)
    44.  
     
  3. Seanm07

    Seanm07

    Joined:
    Mar 18, 2014
    Posts:
    12
    I just reverted the project down to Unity 2019.4.25f1 and I can confirm this version is not affected by the issue.
     
    Last edited: May 20, 2021
  4. Francesco-FL

    Francesco-FL

    Joined:
    May 25, 2021
    Posts:
    176
    I also encountered the same problem updating from 2019.4.25 to .26

    I encountered the problem with a samsung galaxy s4 mini (4.4.2)

    With the .25 version everything was fine, with the .26 it crashes on startup

    I filed a bug report on May 8th but they still haven't told me anything
     

    Attached Files:

    • 1.png
      1.png
      File size:
      49 KB
      Views:
      288
    • 2.png
      2.png
      File size:
      50.8 KB
      Views:
      284
  5. Francesco-FL

    Francesco-FL

    Joined:
    May 25, 2021
    Posts:
    176
    gamedev1232018 and Seanm07 like this.
  6. Francesco-FL

    Francesco-FL

    Joined:
    May 25, 2021
    Posts:
    176
    I forgot, remember to vote it if you want unity to take care of it as soon as possible. (I don't really know if the votes work like this but I think so)
     
  7. HT93Studio

    HT93Studio

    Joined:
    Dec 23, 2018
    Posts:
    1
    I voted
     
    Francesco-FL likes this.
  8. Francesco-FL

    Francesco-FL

    Joined:
    May 25, 2021
    Posts:
    176
    Update:

    in the email it was also said, in exact words:

    "After further investigation of your issue, it was resolved as a duplicate of this issue:
    https://issuetracker.unity3d.com/product/unity/issues/guid/1331290"


    This bug has been fixed for
    2021.1.9f1
    2020.3.11f1
    2019.4.28f1

    versions 2020.3.11f1 and 2019.4.28f1 have not yet been released, we'll see
     
    N_Richard and Seanm07 like this.
  9. N_Richard

    N_Richard

    Joined:
    Jun 10, 2020
    Posts:
    1
    Thank you for the update.
     
    Francesco-FL likes this.
  10. Francesco-FL

    Francesco-FL

    Joined:
    May 25, 2021
    Posts:
    176
    Version 2020.3.11f1 has been released and I confirm that the error has been resolved
     
  11. Francesco-FL

    Francesco-FL

    Joined:
    May 25, 2021
    Posts:
    176
    Version 2019.4.28f1 has been released and I confirm that the error has been resolved