Game crashes when joining on Android device?

[daniellochner]

Hi there,

For some players, the game crashes when joining/creating a game when using an Android device.

Here is a link to a forum post in which others are experiencing the same issue:
https://forum.unity.com/threads/getting-a-lot-of-libil2cpp-so-crashes-in-android-build-after-implementing-unity-multiplayer.1401385/#post-9051061

I can recreate this myself on my own device using Bluestacks 4.

Unity: 2021.3.22f1
NGO: 1.3.1
Transport: 1.3.4

[mtarzwell]

Hello @daniellochner thank you for the bug report. Can we get a bit more details to help with troubleshooting?

Please provide:

• Android device details
• log files and/or error messages that appear at the time of the crash
• reproduction rate: is it 100% of the time, or sometimes?

Thank you!

[NoelStephensUnity]

Hi @daniellochner,
I posted a response in the thread you referenced, but to summarize:
Since you are using NGO v1.3.1, if you have code stripping enabled then you will most likely get a crash. The easiest fix would be to update to NGO v1.4.0 which has a fix for that (if you are using multiplayer tools then make sure to update to the most recent version as well since that package recently had a fix for a similar code stripping related issue).

Let me know if this resolves your issue?

[daniellochner]

Hi Noel,

Thank you, but it didn't seem to fix all the crashing unfortunately.

I can create and join servers on my computer using the Bluestacks emulator, but when I asked a player who was crashing on his phone, then it still crashed when he tried to create/join a world.

As you can see in the following screenshot, however, he seemed to crash right after he joined! So his connection was registered.

Would you mind letting me know what version of Unity you are using? I am currently using 2021 LTS, but am upgrading now to 2022 LTS. NGO, Transport and Collections etc. don't prompt me to upgrade in the package manager (I have to specifically include the version codes). Could that be causing issues?

[NoelStephensUnity]

Just to leave no "stone unturned":
Did you make sure the remote user connecting from their phone was using the updated version built using the NGO v1.4.0 package?

[NoelStephensUnity]

If so, then if you wouldn't mind trying:

• Have you tried building with NGO v1.4.0 and removing the Relay QOS package?
  • There could be a code stripping issue in that package.
• If the above does work, then try building with code stripping turned completely off (for the time being)

Let me know if either of the two above approaches (and which one) stops the remote user crashing issue (if either do)?

[daniellochner]

Yes, he was definitely using NGO 1.4.0! I will try removing the Relay QOS package though and reporting back.
How would I turn code stripping completely off? There appears to only be the option to set it to "Minimal".

[daniellochner]

Update: It seems I'm unable to remove the QOS package.

[NoelStephensUnity]

Based on that forum thread, it also looks like there is also a crash related to automatically setting the region on Android v8 or v8.1(is the remote client connecting is using that version of Android?).

Regarding turning off managed stripping level ("code stripping"), do you not see a "Disabled" property?

[daniellochner]

No, here are the options I have (Unity 2021.3.22f1).

[NoelStephensUnity]

Ahh, you are using IL2CPP as your scripting backend as opposed to Mono.
For production builds (i.e. Alpha, Beta, and actual release) that is the better choice, but for debugging I would suggest using the Mono scripting backend:

When you switch to Mono as the scripting backend, you should be able to completely disable managed code stripping (for testing/debugging purposes).

[daniellochner]

Hi Noel,

Some progress: When I force set the region to "europe-west-2" like in the allocation settings (as the forums thread suggested), it allowed the user to create a world, but no-one else could join him.

This is obviously not a solution, but it at least confirms that there is indeed a problem with QOS.

I will switch to Mono now and disable stripping entirely, but please could you have a look into this? Now that it is confirmed that there is actually an issue with QOS.

Note: I actually reverted back to NGO 1.3.1, because there was some change that broke something for me in 1.4.0 (to do with asynchronous scene loading). I'll upgrade back though and see what is now going wrong there...

Thanks.