Unity-Technologies / Unity-Technologies/com.unity.webrtc

[BUG] Android app crash on launch

Open
#437 55 comments 1 reaction 1 assignee View on GitHub

@karasusan is already working on this.

Since Jun 13, 2021.

bug issued
Dominant language
Assembly
Stars
852
Forks
238
PR merge metrics
No merged PRs in 30d

Description

Android build crashes as soon as it launches if the plugin is installed. The crash happens before any C# script runs.
This is not a solution but just to check, if I disable "Load On Start Up", the app launches then crashes when it tries to initialize the library.
IL2CPP and arm64 are selected, I have also tried various android API versions but no luck. Are there anything else to check? What related software versions do I need to use for this lib? Any info appreciated.

Reproducible step on my system is quite easy as follows;

  1. create a new empty 3d unity2020.3 project (currently trying on 2020.3.0f1)
  2. set the build target to android, select IL2CPP and arm64
    --> try to build and run at this point. It works.
  3. import webrtc 2.4.0.exp3 (no need to write any code.).
    --> now build and run again, then you get the error.

The log looks like this;

06-13 15:48:12.153: E/CRASH(17882): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-13 15:48:12.153: E/CRASH(17882): Version '2020.3.0f1 (c7b5465681fb)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
06-13 15:48:12.153: E/CRASH(17882): Build fingerprint: 'google/flame/flame:11/RQ1A.210205.004/7038034:user/release-keys'
06-13 15:48:12.153: E/CRASH(17882): Revision: 'MP1.0'
06-13 15:48:12.153: E/CRASH(17882): ABI: 'arm64'
06-13 15:48:12.153: E/CRASH(17882): Timestamp: 2021-06-13 15:48:12+0900
06-13 15:48:12.153: E/CRASH(17882): pid: 17882, tid: 17904, name: UnityMain >>> com.DefaultCompany.IL2CPPTEST <<<
06-13 15:48:12.153: E/CRASH(17882): uid: 10321
06-13 15:48:12.153: E/CRASH(17882): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-13 15:48:12.153: E/CRASH(17882): Cause: null pointer dereference
06-13 15:48:12.153: E/CRASH(17882): x0 0000007afe64da90 x1 0000007a87015dbc x2 0000000000000013 x3 737968507465476b
06-13 15:48:12.153: E/CRASH(17882): x4 0000007a87015b76 x5 0000007a859e9e8c x6 7665447465476b76 x7 41636f7250656369
06-13 15:48:12.153: E/CRASH(17882): x8 0000007afe64da90 x9 0000000000000000 x10 0000000000000000 x11 0000000000000000
06-13 15:48:12.153: E/CRASH(17882): x12 6563697665447465 x13 72646441636f7250 x14 0000000000000107 x15 0000000000000012
06-13 15:48:12.153: E/CRASH(17882): x16 00000079a7f73208 x17 0000007d7e9e02c0 x18 00000000ac3b7fa9 x19 0000007a01083f78
06-13 15:48:12.153: E/CRASH(17882): x20 0000007a872efd78 x21 0000007afe64da90 x22 0000007afe64d990 x23 0000007bae6a8110
06-13 15:48:12.153: E/CRASH(17882): x24 0000007a01083f60 x25 0000007a01083f78 x26 0000000000000000 x27 0000000000000000
06-13 15:48:12.153: E/CRASH(17882): x28 0000000000000000 x29 0000007a00c43d80
06-13 15:48:12.153: E/CRASH(17882): sp 0000007a859e9ec0 lr 0000007a86c0365c pc 0000000000000000
06-13 15:48:12.238: E/CRASH(17882): Tombstone written to: /storage/emulated/0/Android/data/com.DefaultCompany.IL2CPPTEST/files/tombstone_00

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.