Windows and apk versions have been doing this for the past, like, 20+ updates. You never fix this issue so it's never playable. It's a syntax error, which means it's on your side. Just fix it already.
Android, but I did it on Joiplay too (with the Windows version) and got the same on both. Since this happens in the apk, it's not a Joiplay error, and since it happens with Joiplay it's not a generic android error.
The strange thing is that my phone is fully updated (I've manually forced all possible updates), but I didn't get this issue on my old phone which was super outdated yet ran the game for a while despite crashing due to low ram. My current phone's specs are outstanding and I never have space or ram issues, yet this is the only game that gives me a syntax error or any kind of crash error on launch other than 7z files (but that's a whole other issue).
It has to be something to do with the browser your phone is using, which determines what version of node gets used, and there seems to be one that isn't supporting a Javascript keyword somewhere. The upcoming update that expands error reporting should tell us where it is. Once we know that we can look at changing it to something that's compatible with older versions.
You mean node.js right? I never knew it used the device's default browser to run the report. The more you know!
And again, my current phone is more updated than the old one, yet the old one could launch the game just fine. This game is actually the reason why I fully updated my device in the first place, so it's been tested with multiple android versions. That's why I said it shouldn't be a driver or compatibility issue.
But we'll surely figure it out in the next version. :)
Yeah, for some reason node.js comes from the device rather than what's packaged in the apk when you're playing on mobile.
And your phone itself and the OS might be more updated than the old one, but the browser on it may still be using a version of node that doesn't support a command that your old one did. We'll have to wait and see what the error reporting gives us to work with. :)
Hey, something that may help, both prove that it's not your fault or in the event that it is, help locate the exact issue, is to update your error reporting to include some of the stacktrace, it's not something that will make any sense to the end user, but when they report errors it can be an absolute confirmation that it's not a development error, or provide you the exact location of the issue when it is a development error.
I don't know what logging framework you utilise, but most of the standard ones allow stacktrace reporting when a fatal error occurs. This would cover your bases & make the debugging process much easier on you.
Sorry if you already knew that, best of luck with your game.
The game already has a logging framework that outputs a crash log. Whatever issue this is it happens before it even initializes. From past experiences, this happens because of something being outdated, making it unable to parse the javascript code.
The largest issue is that the bug is absolutely not reproducible on my side and is only encountered by a small percentage of players and most of the time driver updates or similar have resolved it.
Why would a link to the thread be needed? The important part is that we fixed it.
If you absolutely need it for some reason though: https://www.reddit.com/r/JoiPlay/comments/171f7gr/can_anyone_help_methe_game_sta...