I am quite ok with 2018R4 (Win desktop + console) now. While I am busy coding, I will postpone the move the the new version, just to avoid possible issues popping up when facing the deadline of the project.
Do you want to find out what causes the bug or not? Or you can reduce the app until the bug goes away. Which I always think is the most awful process of all.[/quote]
To be fair, replacing websockets with curl would not be easy either. Theyre more like a persistent TCPSocket than an HTTPSocket.
I thought the websockets were typo because the OP talked about a desktop app. Checking, no, he didn’t. Sigh again. Then he has to go through the extreme fun of reducing the project until it doesn’t crash anymore.
That is, unfortunately, quite common with Xojo. In my case, 2018r3 worked well (but I couldn’t get a license since r4 was already out), 2018r4 did not work at all, and 2019r1 works well for me[/quote]
A current Xojo license will let you compile any earlier version.
I have been building an app that makes extensive use of sockets throughout the beta period and now with the release version and have not had any problems with that. I havent released anything compiled with 2019r1 yet, but am just doing a final build for testing now and will let you know if I have any problems. I am aware that they made changes to the new URLConnection class, but I dont know if there were any changes to anything lower level than that.
The best thing you can do is to zip up the project and open a private feedback report to Xojo. If they can duplicate it then they can fix it, if you cant collect any other info about where its happening then this is the best option. Otherwise they wont even know where to start.
As @Stéphane Mons said, that is, unfortunately, quite common with Xojo.
I still have to use 2016r4.1, for one proyect, 2017r3, for 2, 2018r3 for most and 2019r1 is working ok with the one updated to URLconnection. Sometimes Rewriting the code when xojo breaks the “framework” just to use the last release is not really worth it.