yesterday, the relase date was… yesterday
2 Likes
By my clock it’s still (barely) the day before yesterday. Yesterday will be here in about 45 minutes.
2 Likes
Well, if you go to a certain place in the arctic, you can stand in all the time zones all at once. Then you are in today and tomorrow at the same time. Yeehaw.
3 Likes
LOL you’re not alone. I’ve been refreshing certain web pages like a crack-addicted lab rat hoping to see a release.
1 Like
Still shows the previous version. I guess it gets formally released during business hours or something?
Still more than 16 hrs of 2026-07-08 in Austin, Texas where Xojo is from.
I guess it will be released within those hours.
@Emile_Schwarz Where are you located that you were already in 2026-07-09 at the time that you posted?
Has arrived 
4 Likes
I’ve been super excited for this release too. Some great updates in R2. Feels like Christmas!
1 Like
Merry July 
I agree it is a very anticipated release
Yeah this is enough for me to probably renew when the price is right.
1 Like
France.
I may not say so in my op, but the first time I get the Release Notes for Xojo 2026r2, the date was 2026-07-07.
I do not asked because I do not needed, and waited for the next day. So, yesterday I d-saw the day change and went a bit afraid on what that would need.
I waited a bit after the usual release hour (Paris Time), then saw nothing ans asked here because someone (a tester) asked a question in the forum about that version.
I shared the screen shot to let everyone including Xojo) that I have no inside information (that I do not disclose confidential | internal data but publicly available data).
2026r2 is one of the nastier updates in the last years: my apps crash on quit and a code pattern that has worked since the times of Matt Neuberg crashes, too.
1 Like
Bad news. I downloaded it but have not time to install / use it.
I will wait a bit…
I had a crash on quit with earlier betas. It was fixed in the later. Mine was related to not having a DesktopQuitMenuItem in the app.
I know yours was both API 1 and timer related. Does it still persist in the release?
I just tested with the final release. The crash is not timer based. I can reproduce it in debug but not the built app. Or I haven’t tested often enough. I’ll let Codex add some instrumentation.
Is this not the null object in a timer event issue, that you had? That’s the one I recall you talking about.
2026r2 is full of “we didn’t know that’s how that worked” type changes that, as usual, didn’t get enough testing. It feels like somehow I know more about the history of the framework than they do.
I haven’t been able to build the SSH helper for Lifeboat with 2026 releases because of these untested changes that break long-working code and I haven’t the time or care to figure what they really broke.
I’m shocked to see people calling this a monumental release worth renewing for.
Too many issues to remember.
Crash on quit: don’t know, yet, what is causing the crash.
Code since the times of Matt Neuberg: have a modal window with an init method to return a value. In the init method the window does a showmodal. The buttons in the window close the window. This now crashes in 2026r2. A “window.hide” instead of “window.close” seems to fix the crash. But I use that pattern like 10 times or so in the larger app.
1 Like
(post deleted by author)
Isn’t window.showmodal forbidden since some years as it would crash the app? I remember changing all occurences a while ago…
1 Like