Ed Palmer

Bring all the version information into synchronization even if it isn't the final version designation for the next release.

Unhandled Exception Erro

Fix committed to trunk in revision 1740.

Fix #361. On macOS 26 (Tahoe), App.Activate was being called before App.Open had run to completion. Add a flag in App.Open to indicate when the initialization in App.Open is completed and the MainWindow is about to be shown. Check this flag at the start of App.Activate and exit if initialization is not complete.

Unhandled Exception Erro

Issue is confirmed and reproducible on macOS 26.0 Beta (25A5346a) running in a Parallels VM. App.Activate is getting called before App.Open has completed. This means that on entry to App.Activate the first time, DebugWriter has not been initialized and is Nil, causing the NilObjectException. More research is needed to determine the best option to avoid the race condition. Until I can fix this and post a new build, OpenSong should not be run on macOS 26 (Tahoe).

Interesting. The stack trace points to a routine (App.Activate) that has not had a reported issue before to the best of my knowledge. The error is a NilObjectException, usually caused by an internal object not being initialized. The code could use some additional error checking, but that would only help identify which object isn't initialized and not why it isn't initialized. I do not have a system running the macOS 26 beta to test; my two Apple Silicon Macs are production systems that need to stay...

Modify macOS-specific build processes to match the latest Xojo features for automatic code signing of Apple applications.