It would be interesting to hear about surprising technical issues that you ran into and maybe solved while developing and publishing.

My experience has been that Godot tends to be unpredictable once you start to publish on multiple platforms, but I'm not sure how to prepare for such surprises.

These are some of my issues that caused some grey hairs around this jam:

MacOS export doesn't seem to be possible from Windows, but the error message is a cryptic "Invalid bundle identifier: Bundle is missing"

HTML5-export does not display 3D-graphics correctly in MacOS, even in Chrome. I used GLES2, but rendering in MacOS is strangely selective. Some models render properly and some not at all.

Non-debug native export results in a grey screen with no indication of what went wrong. Debug-enabled version works fine.

I read this might have something to do with using typed GDScript. But does this mean types should just be avoided or is there a workflow for debugging such issues?

When we export to HTML5 and clicked the option something along the lines of "export entire directory" the tile map resources has a 90 chance of getting excluded... So sometimes exporting feels like a russian roulette before we manually selected each file to export. xD

Ive had a few, some my fault some engine bugs.

The 3.4 version of godot failed to export HTML correctly. The sound was choppy and the keyboard events were dropped after losing focus. Even after clicking back on the game. The solution for me was to use 3.3.4, which worked perfectly.

Some of nodes used a particle2D process material. Changing the speed of the particles in one instance of this node affected all the others. To be precise, the last process function that was executed affected all the others. The solution was to make the resource local to the scene. I have seen this button many times but didnt understand it up until I ran into this issue. Also the same for some collision shapes.

Other than these it was pretty straightforward.

I'm an amateur when it comes to scripting and my push blocks are non-functional if they get anywhere near each other. I did not design them in an expandable way. so every level with more than one is set up in a way so that they can never get near each other. I do have a solution now, but didn't implement it in time. That does mean I can make some level ideas involving multiple blocks close together.

I found the reason for my game freezing when exporting without debug: I used assert() when connecting signals.

Apparently assert() only works in debug mode and fails silently when exporting without debug.

Officially assert lines are supposed to be completely ignored, including any statement that's inside the assert. In this case, the game just froze even though it supposedly should have loaded the main-scene and run without signal connections established.

We designed a nice-looking parallax background only to find that we couldn't get the ParallaxBackground node to work properly. When asking around the community for help, there seemed to be a general consensus that this node is confusingly designed.