PureBasic 6.30 does not start on macOS Tahoe – NSToolbar exception

[Atari]

Dear PureBasic Team,

I would like to report an issue where PureBasic 6.30 does not start properly on my macOS Tahoe system.

When launching the application, only the PureBasic splash screen appears. The IDE window never opens and the application becomes unresponsive. It does not quit automatically; it must be terminated manually using Force Quit.

According to the system log, the issue appears to be related to an NSInternalInconsistencyException during NSToolbar initialization. The relevant error message is:

“NSToolbar already contains an item with the identifier 0. Duplicate items of this type are not allowed.”

It seems that the IDE attempts to insert a duplicate toolbar item identifier, which macOS Tahoe’s AppKit implementation no longer allows.

Removing the Saved Application State and preference files did not resolve the issue.

System information:

PureBasic version: 6.30 ARM64

macOS version: Tahoe 26.3

Hardware: Apple Silicon Mac Mini M1 16G RAM

I can provide the full system log if required.

I would be grateful for your assistance in resolving this problem.

Kind regards,
Zoltan Kiss

[mk-soft]

I don't have Tahoe 26.3 and no ARM64, but the current Command Line Tools version: 26.3.0.0.1.1771626560

When testing with macOS 15.7.4 (Intel) and a code with double ToolBar item, the error also occurs here.

[15:19:30] Waiting for executable to start...
[14:19:30] Executable type: MacOSX - x64 (64bit, Unicode)
[14:19:30] Executable started.
[15:19:30] [ERROR] Line: 279
[15:19:30] [ERROR] NSToolbar 0x600000e219a0 already contains an item with the identifier 0 0x600000e219a0. Duplicate items of this type are not allowed.

I once recompiled the IDE pb V6.30 as a demo and the error does not occur. Thus, the IDE code is ok so far

Maybe someone can test the demo version with Tahoe 26.3.

[WilliamL]

I can run 6.30 fine on my machine running Tahoe 26.3.1. I seem to remember having some odd behavior when I went to Tahoe but they seem to have gone away. I am seeing the same problems in 6.30 that I have reported in Mac Bugs.

I don't know enough about the system to help with your problem but it does work here.