Whoops! Thanks! I kept thinking it was code related and didn’t check this part of the release notes! Sorry for the false alarm!
Amazing! It works! That was a quick turnaround. 
This may not seem like a big change, but to me it’s really useful. It unlocks all sorts of possibilities with static curved terrain and dynamic bodies. For example, games like Hill Climb Racing can now be made using the built-in Box2D and doesn’t have to rely on a third party extension!
9 Likes
I am not sure how to report this but…
I have been using the beta (1.13.0) for a while now and I accidentally submitted an Android Bundle exported from it (Defold 1.13.0 Beta) on Monday, 2nd June 2026 and it got rejected this morning; 4th June 2026
The reason being:
The update was for fixing some GUI Text Nodes in the extras section and nothing else. It was a hotfix since the nodes shouldnt be visible on any platform apart from Android, thats why I missed them. When I received the email is when I went to check on these “stability issues”
I did not get a crash, but the title screen and about section in my game are not displaying content as they should. Every other collection renders as it should.
I unistalled the 1.13.0 version and reinstalled the latest 1.12.4 version from the playstore, which was updated just 2 days before; 31st May 2026 and it doesnt exhibit these issues.
What could be wrong?
I am using the orthographic camera extension and at first, I thought it would might be the cause but Nope, I dont have the orthographic camera go, as well as any camera component in both collections so Im wondering what the issue would be since both of them seem camera/viewport related.
1 Like
If you uploaded symbols to your Google Play Console together with the release, you should be able to filter crashes by app version and see the exact crash stack in the crash they expirienced.
I actually did not upload the debug symbols, or even test with the internal, closed testing track. I just thought, these are just simple text corrections I missed. Gonna fix them and thats it.
I was initially planning on creating a bundle using 1.12.4, test and submit so that it passes. So now do I upload the debug symbols and resubmit the 1.13.0 version to report back with the crash stack?
1 Like
Yes, please. Also, I recommend you always upload symbols. You never know when it will be useful (it is a separate option in the uploading screen)
I tried and realized the following:
Even if I upload symbols and attach them to the bundle that failed, I cannot proceed with submission again, unless I upload another bundle with another version code
So I tried just that, instead of 11, I did 12 and it worked; only problem is, I did that to the internal testers track. The original issue was done in the Production track and I cannot use the debug version along with the debug symbols in that track.
I can try that, but for me to get any response, it will take 2-4 days…
For now I can only profile locally with the Internal Testers bundle, alongside Android Studio and I still cant reproduce the crash.
1 Like
We’ve found an issue while attempting to run a 1.13.0 build on our lowest-end test devices, a ZTE Blade A52 and an Alcatel 1S 5028D.
Whereas a version built with 1.12.4 loads perfectly, when building the same commit with 1.13.0 the game loads to a black screen 95+% of the time. The black screen remains visible for a long period of time (up to 10 minutes) and then the game shows the first frame.
This does not happen on any other of our Android test devices (Samsung A13, OnePlus Nord 2, Xiaomi Redmi Note 10 5G), nor does it happen on any iOS device.
As far as I can tell, these devices share very similar GPUs (PowerVR Rogue GE8322 and GE8320), but everything else about them (CPU cores, OS version, architecture, etc) is quite different.
I’ve opened an issue here: Android build gets stuck on black screen in 95+% of app opens on ZTE Blade A52 and Alcatel 1S 5028D · Issue #12570 · defold/defold · GitHub
2 Likes