The problem could lie in the fact that this is a Construct 2 project being imported into Construct 3 and switched to runtime 3.
There are apparently many problems with this approach ( Importing into Construct 3 and staying with runtime 2 seems fine )
First thing I notice is that it doesn't go straight to bar and logo screen then jump into my own loader layout. There is just a bar that pops up before it goes to bar and logo loader, but often it does not go there at all, just black screen.
My custom loader text or bar seem not to work either, so you can click on continue before anything is really loaded.
Often if you do get to theis loader layout clicking on continue just shows a black screen, reloading the app or browser then seems to make it work sometimes.
In the latest betas, all of my particles do not show up for some reason when playing it on a phone, but everything seems fine on PC. Opening an empty new project in Construct 3 then copying/pasting asteroids and particles + code used in Construct 2 game, works fine. So, maybe something lost in translation between Construct 2 file and Construct 3 ( In stable version 148 this works fine )
Most of the games do not work at all on my phone when using remote preview, if switched from runtime 2 to 3 ( stable 148 does not have this problem, ).
I know I should file a proper bug report, but I don't have time to re-create simpler versions of these projects. Right now I will either use Construct 2 to export, or Construct 3 using runtime 2. Weirdly enough a problem with janky physics on some phones disappears when using Construct 3 / runtime 2 combo.
By the way, I have never used any 3rd party plugins, only Construct 2 events/behaviors