During the last several days I tried to launch my game on Android but it constantly crashed. I thought that it was too heavy, that it lacked RAM etc. I removed almost everything from it but it continued crashing. When it was obvious that there is no lack of the RAM because the game had consumed 2 GB on Windows, I started to dig deeper and look for the other errors, and, after another day of suffer, found that there had been some plug-ins incompatible with Android in my game. Removing them forced the game to work! But it is horrible that there is nothing notifying about the actual problem! I think it would be better if the game crashed with some message like “Incompatible plug-in!” instead of the silent crash. @SupportiveEntity, could you pay attention for this?
Hey there @Etyuhibosecyu! That’s one of the less fun parts when working with mobile builds, as that errors before or during compilation, are usually rather verbose and relatively straight forward to track down. For the fully compiled mobile game however, this can often be difficult. In many cases, the error itself may not stem directly from the plugin, but rather indirectly with how it interacts with other features.
For example, if a plugin uses tech that isn’t available on mobile builds, it should fail during compilation and have a clear error. However if the plugin does operate, but some data is different than what is expected, the function (in the base engine) that calls it will be blamed. Following the stack trace back can help, but it’s not always clear without attaching a debugger and stepping through the problem.
Some plugins do have warnings prior, but usually in their documentation or in the source. Third party plugins aren’t forced to check compatibility with other systems.
This resource can help get a debugger attached in Android Studio to help identify issues:
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.