Game doesn't open on mobile after this update :[
Viewing post in Vinculike (18+) - Prototype comments
Hello there! Huge thank you for the report. I’m playing it on mobile right now and it works without issues. I have Android 11.
Can you please provide a bit more details on your setup? Maybe something got broken with the newer Android version? Already happened in the past.
Also if you can tell me something more specific about what exactly is the error you’re getting. Does it “start opening and then just closes and you see it in “all apps” as black screen - clicking it there repeats it again”? Or something else that might give me a hint what’s wrong.
Meanwhile I see that the app crashes on my ancient Android 5.0, let me see what’s wrong there, maybe it is the same issue?
EDIT: Meanwhile I returned the older Android version to list of downloads. I’ll try to figure out what went wrong with the new one ASAP.
EDIT2: I see a potential culprit in the logs on Android 5.0. Investigating…
hey sorry for late reply! I know the fix is already out but my model is a SM-G99U1 using version 13!
It use to open for a split second and just closed, it had said something was wrong with the app and to wait for a fix. Sorry for late reply again, completely forgot to comeback here to see if you responded
Huge thank you for the information! Can you please test the newest version if it works for you. Because unfortunately I believe I’ve discovered a new issue. The issue that was fixed in the latest release - the game was starting properly but crashing when trying to “Start New Game”. However, there was a second issue I’ve found on Android 5.0 that the game crashes as you describe it - starts, blinks black screen, and closes. I’ve talked with the Castle Engine developer and we hoped that it’s caused by old 32-bit devices. But if your, newer device may also be affected, then this issue will take a higher priority to fix. So, please test if the game works for you. Unfortunately if it doesn’t, I highly doubt that it can be fixed before the Tuesday (and as this bug is quite weird, hypothetically it can take longer time to find the solution).