The game seems fine when I test from the editor but on my Galaxy S8 it crashes immediately after the Unity splash screen.
I’ve gone about collecting logs in a few different ways initially using CMD/ adb but also with the Logcat package from Package Manager.
The problem I face now is just the sheer volume of text here. Even when I filter the log by setting the priority to “error” there are so many lines and they mean so little to me I have no idea where to start.
Can anyone suggest what sort of thing I need to be looking for? Is it ok to post up logs here to get advice? If so, what format is appropriate? Do I need to filter them? Do I post it up as a text file or in between code tags?
Many thanks.
D
Enabling filtering by package, that will show logs only for the specified app.
The downside here is - package selection only works on running apps, so if it crashes fast, you won’t be able to select it via package selection UI.
In case that happens, leave package selection set to None, and search for at least one message belonging to your app, right click on the message and do filter by PID
Cool. So that brings it down to 4860 lines. Most of it is red text (Priority: Error) but unfortunately the messages are just file paths and combinations of letters/numbers. There’s nothing I read that looks like something I could investigate.
Could you show some of those messages?
- Output removed incase of security issues. -
Have you tried to just launch a debug version to the phone connected to unity?
Most all crashes I’ve had on Android unity debugger will identify it (unless I’ve just been lucky)
I found the problem! Embarrassingly it WAS actually showing up in the editor output, it was a stack overflow problem with an old version of a script still attached to an object in the scene.