Sad. They probably will release a series of rapid releases trying to stabilize the mess they introduced with their previous “deeper security” measures. Some problems probably they will blame other software, like MS Office and will ask them for changes. Let’s see how it develops. I didn’t have the courage to play with macOS 14 yet. I need reports of stability for few weeks, a thing we never got since 14.0.
1 Like
This is why there is an advantage to having a dedicated Mac for development. I need to support users on Sonoma so I need to be running it, but I most definitely don’t want it on my everyday machines for personal use.
I just say “not supported yet”. The irremediable crashes are on those not obeying the policy.
Upgraded my testing machine recently and it has been a real PITA. Couldn’t even get the 14.1 update through software update, it just never completed checking for updates so I finally booted to recovery and reinstalled the OS from there so that got the most recent version. Things that in older OS versions would only have hung the app are now hanging the entire machine, but only sometimes. When just the app is hung and I force quit it to get it going for more trying to figure out what the heck is going on, all the helper apps and child processes that this program uses are left behind still running. How is this a good thing? It should kill all the child processes when you kill the parent shouldn’t it? It always did before. Sigh… I’m currently updating all the helper apps to have been built with the latest versions of all plugins and Xojo versions so that I can rule that out, but this is really miserable. I expect a certain amount of pain when doing a major update but this is really kicking my backside and depressing me.
So… I’m still frustrated but also amused. It turns out that 100%, (well almost) of my difficulties were because I had a failing hard drive connected to the machine. Not a single file system error! Not a single error from anything that did not result in a hard hang of the app, which could then be force quit, but could not be restarted and the entire system would kernel panic upon trying to reboot the entire machine. How can all the file system stuff not throw an error but instead just hang up or wait for ever for something to happen? So it’s not as bad as I thought, but it’s still frustrating. In my memory the OS has never been good at handling file system errors, but it seems worse lately and not better. In any case I’m up and running again until the next disk starts to throw errors that don’t show up anywhere.
1 Like
It makes more sense when you stop thinking that a Mac is a computer and start thinking that its a glorified iPhone with a Desktop like interface duct taped atop of it.
1 Like
While debugging, using GetOpenFolder or the variants will display an ‘Open’ dialog, but clicking the action button either does nothing, or moves the dialog down the screen.
For me, the only way to select a file is to double click it in the Open dialog.
Thats pretty frustrating
I do not use these, I do not saw bugs.
Better: some crash I was acustomed with disapeared with Sonoma.
I am eagerly waiting 10.5 for Search files and Renumbering files bug corrections.
Can you share your list of Sonoma bugs ?
In every of your apps or a single one?
In every of your apps or a single one?
“The” important one.
I couldn’t recreate it this morning in a new near-empty project.
But starting a new project forces API2 and I suspect it is possibly something to do with using predominantly API1 code.
(This is going to be more common over the years… I am so angry about API2 that I can’t discuss it objectively)
The code that both fails (big project) and works (one dialog, API2)
Edit: The issue is with clicking the Open button using a mouse.
If I tab to it, so that it has focus, and press spacebar, that works.
dim thefile as folderitem
//thefile = GetOpenFolderItem("*.png")
thefile = folderitem.ShowOpenFileDialog("png")
if thefile <> nil then
if thefile.exists then
//do stuff here..
//when it fails, this line is not reached in debug.
//Works in compiled
end if
end if
It’s indeed working fine in a new project (so, an API2 one).
If it happens “only” in your important project and not in a single other one, then this has something to do with that project. Have you tried trashing the plist file that MacOS keeps to store per-application navigation dialogs settings? It may be corrupted and produce unexpected results.
Otherwise, something specific in this project (like using DoEvents 
).
I’d try showing an OpenDialog early in the project, like as the first lines of the App.Open event, just to test there’s nothing interfering later. That is, if you’d like to isolate/reproduce the bug.
I don’t have such a list. I realize that Apple is having a hard time with Sonoma. I wonder if they hired developers that were with Microsoft - Windows 11 is also a nightmare where things re broken much too often.
Don«'t get me wrong, I love MacOS, but changing things that work well, I don’t get it.
Just bad management using the usual devs.
The marketing direction deciding features and changes, and saying “do it” without mature designs and setting unrealistic time frames for stability, and having a vision of “not a problem, later we can fix the bugs”.
Money grabbing is running over the quality, over time it will affect sales.
2 Likes
That’s true if you use a new IDE but if you use something before 2019r3 to create the project, it should also show the API 1 stuff, even in a new IDE.
Yes, but you get the current documentation.
Oh… and in your everyday life, this is the pnly time ?
I saw on TV what building a small parking (near it) do to the auto highway near there (A13, near Paris: many days closed).
We, usually, NEVER know the reasons why of nearly each and every change.
Back to the topic:
No, I do not think Sonoma is the most instable macOS ever.
So, from 10.x+ (macOS brand series), which is your most unstable candidate and why?
I spoke too soon…
In Safari, I lost all my opened windows contents…
I am sure this is unclear.
I get a “low SSD available memory” information, then I closed some running applications (Xojo, …).
At that moment, I had Safari open with some windows and some tabs.
I had to close everything shut down, Power On.
When I needed to fire Safari, I get my windows, but no tabs, nothing in the windows… 
Weird.
Also: I do not care about other macOS versions; I use one and concentrate on that one (even if I still have El Capitan on my MBP i5). My MPB m1 runs the last Sonoma (last release, no beta).
Closing apps to free disk space might not be the right approach, as most apps try to save their state when the are closing…