URGENT BitBox-4.41.0-macOS fails opening at all on MAC 14.3.1 (23D60) Sonoma

[vigilant4u]

Version 4.41.0 nor any older Version of Bitbox is opening on MAC Book Pro M3 Silicon equipped Macbook.
The OS is Sonoma 14.3.1 (23D60)
Rosetta 2 as opening option is also impossible as the app, when right clicked on "Info" , although showing that is optimized for "INTEL" does not show up the option to open it via "Rosetta 2" although installed on my mac with the newest version.

I need urgent help as i was migrating from an intel based mac to a total new Macbook Pro M3 SOnoma equipped machine.

There is also no log, as the log normally is safe in the folder "Application support" then "bitbox".
But there is not folder at all, as the app refuses to open and crashes even before opening.
Of course the bitbox itself was plugged in via USC c before.
Thx for a quick support.

[benma]

We tested it on a macOS Sonoma 14.3 and the app launched normally.

Could you try opening it from a Terminal opened in the same folder as the BitBox app and running:

./BitBox.app/Contents/MacOS/BitBox

Maybe the terminal will output some helpful information.

About the "Open it via Rosetta 2" option: Intel apps generally automatically launch via Rosetta on M1/M2/M3 - I also don't see an explicit option like that in the menu.

[vigilant4u]

We tested it on a macOS Sonoma 14.3 and the app launched normally.

Could you try opening it from a Terminal opened in the same folder as the BitBox app and running:

./BitBox.app/Contents/MacOS/BitBox

Maybe the terminal will output some helpful information.

About the "Open it via Rosetta 2" option: Intel apps generally automatically launch via Rosetta on M1/M2/M3 - I also don't see an explicit option like that in the menu.

App crashes again. Be aware: I use: Sonoma 14.3.1 - No helpful information from the terminal app. Very annoying. Why dont you publish a universal app, as most other developpers do, so a native silicon code + an intel code in the app? As of now i cannot use the app at all any more. The problem persists even if i install older version back to 2022.

[vigilant4u]

We tested it on a macOS Sonoma 14.3 and the app launched normally.
Could you try opening it from a Terminal opened in the same folder as the BitBox app and running:

./BitBox.app/Contents/MacOS/BitBox

Maybe the terminal will output some helpful information.
About the "Open it via Rosetta 2" option: Intel apps generally automatically launch via Rosetta on M1/M2/M3 - I also don't see an explicit option like that in the menu.

App crashes again. Be aware: I use: Sonoma 14.3.1 - No helpful information from the terminal app. Very annoying. Why dont you publish a universal app, as most other developpers do, so a native silicon code + an intel code in the app? As of now i cannot use the app at all any more. The problem persists even if i install older version back to 2022.

by EtreCheckPro

[benma]

What is the screenshot showing? I am not familiar with the tool.

It is not clear that the issue has to do with the ARM chipset or Rosetta - generally the current build seems to work fine on macOS M1/M2/M3.

Is there maybe a crash report for the app? A dialog right after crash, or maybe something in Console -> Crash Reports?

[benma]

By the way, until we solve your issue and if you urgently need to use your BitBox02, you could try with Electrum or Sparrow - third party wallets that also support the BitBox02.

[vigilant4u]

What is the screenshot showing? I am not familiar with the tool.

It is not clear that the issue has to do with the ARM chipset or Rosetta - generally the current build seems to work fine on macOS M1/M2/M3.

Is there maybe a crash report for the app? A dialog right after crash, or maybe something in Console -> Crash Reports?

There is no screenshot with proper information that i could send you.
Also the CONSOLE is bringing zero info about "Bitbox" on search.
Nore does Terminal,
nore does etre Check the most powerful tool for checking mac problems: https://www.etrecheck.com/en/index.html

[vigilant4u]

By the way, until we solve your issue and if you urgently need to use your BitBox02, you could try with Electrum or Sparrow - third party wallets that also support the BitBox02.

Sorry but i am not trusting third party apps. This is why i bought the BITBOX!

[benma]

No helpful information from the terminal app.

When running

./BitBox.app/Contents/MacOS/BitBox

Is there any output at all? If so, could you provide the complete output?

[vigilant4u]

Sparrow

just as an info: Both apps are starting without any issues on my MAC . Bitbox 4.41 and any older version: Does not!

[vigilant4u]

No helpful information from the terminal app.

When running

./BitBox.app/Contents/MacOS/BitBox

Is there any output at all? If so, could you provide the complete output?

The only output from Terminal is:

"SingleApplication: Unable to create block.
SingleApplication: 7 "QSharedMemory::create: out of resources"

==> AN NO: REBOOTING DOES NOT FIX THE ISSUE!

The only hint i found, but is is catalina and not SOnoma and i have a fresh and new Sonoma machine right from the start is the following link:

https://forums.developer.apple.com/forums/thread/669625

One more and last thing: /Library/LaunchDeamons/ has created a plist file as attached here: with the following content:
https://www.dropbox.com/scl/fi/u4p8uday70wrf5kjnozdh/ch.shiftcrypto.bitboxbridge.plist?rlkey=u7t3bczpke3zjwcwx67xqp5sr&dl=0

[benma]

Thanks, this is a very helpful message and is the cause for the crash. Something is not working right with shared memory.

There is a chance that macOS 14.3.1 introduced a change/bug there. We need a bit of time to test it on that version and see what is going on.

I understand the reason for not using Sparrow/Electrum, but if you don't enter your seed words anywhere and use it with your BitBox02, you can relay on the BitBox02 screen for confirming transaction details as usual. As a last resort in case you need something working quickly. Another option is to use a different computer or Android phone if you have access to one.

[vigilant4u]

Thanks, this is a very helpful message and is the cause for the crash. Something is not working right with shared memory.

There is a chance that macOS 14.3.1 introduced a change/bug there. We need a bit of time to test it on that version and see what is going on.

I understand the reason for not using Sparrow/Electrum, but if you don't enter your seed words anywhere and use it with your BitBox02, you can relay on the BitBox02 screen for confirming transaction details as usual. As a last resort in case you need something working quickly. Another option is to use a different computer or Android phone if you have access to one.

Good to know where to work on for you guys. Another app with the same issues is: AUDACITY! Only returning to version 2.2 was helping me out here. Please look and update the app the quickest possible as i do not habve an older Mac any more and as i do not user Android for security reasons at all.
When will i be able to expect an update here guys?

[benma]

We tested on macOS 14.3.1 and it still works as expected for us. It seems something in your system is blocking the creation of shared memory segments.

Can you run

ipcs -m

to list shared memory segments, and post the output?

[vigilant4u]

We tested on macOS 14.3.1 and it still works as expected for us. It seems something in your system is blocking the creation of shared memory segments.

Can you run

ipcs -m

to list shared memory segments, and post the output?

Seems no output is generated with: ipcs -m in terminal ?

More experimenting with ipcs brought: For me: Nothing unusual

[vigilant4u]

The Only way i got Bitbox02 app to run properly on Mac OS Sonoma 14.3.1 was writing an executable apple script to be executed on Login Items during the startup process as followed:

As there is definitely a shared memory bug on Sonoma 14.3.1 preventing to let your app start when the default values influencing the default shared memory settings

kern.sysv.shmmax
kern.sysv.shmall and
kern.sysv.shmseg

would stay as defined by apple, the only workaround is as followed:

open ScripEditor:

tell application "Terminal"

if not (exists window 1) then reopen
do script "sudo  sysctl  -w  kern.sysv.shmmax=2147483648" in front window
delay 0.5 --pause for half a second
do script "roae3o7snapokatMZ" in front window

#if not (exists window 1) then reopen
#do script "sudo sysctl  -w  kern.sysv.shmmni=4096" in front window
#delay 0.5 --pause for half a second

if not (exists window 1) then reopen
do script "sudo  sysctl  -w  kern.sysv.shmseg=32767" in front window
delay 0.5 --pause for half a second

if not (exists window 1) then reopen
do script "sudo  sysctl  -w  kern.sysv.shmall=131072" in front window
delay 0.5 --pause for half a second

if not (exists window 1) then reopen
do script "sysctl -n machdep.cpu.brand_string" in front window
delay 2 --pause for two seconds

if not (exists window 1) then reopen
do script "sysctl -a | grep shm" in front window
delay 8 --pause for eight seconds

quit

end tell

Hope this also works others.

PS:
I have no clue why it works on your side guys as i have used a fresh preinstalled Macbook Pro M3 with Sonoma.
I only installed the latest security update 14.3.1 from end of Jan 2024.

[vigilant4u]

The Only way i got Bitbox02 app to run properly on Mac OS Sonoma 14.3.1 was writing an executable apple script to be executed on Login Items during the startup process as followed:

As there is definitely a shared memory bug on Sonoma 14.3.1 preventing to let your app start when the default values influencing the default shared memory settings

kern.sysv.shmmax kern.sysv.shmall and kern.sysv.shmseg

would stay as defined by apple, the only workaround is as followed:

open ScripEditor:

Hope this also works others.

PS: I have no clue why it works on your side guys as i have used a fresh preinstalled Macbook Pro M3 with Sonoma. I only installed the latest security update 14.3.1 from end of Jan 2024.

Nevertheless:
When the system is starting and the script is executed automatically:
You can open the Bitbox app like a charme.
BUT:
If you close the app once and you try to reopen it, it will crash again!

Conclusion:
THERE IS A SERIOUS SHARED MEMORY PROBLEM in the bitbox app.
I strongly recommend to transcode the app to native Silicon ARM code or to at least make the app a UNIBVERSAL code app having both codeworks included.

PLease:
FEEDBACK: URGENTLY

[pablogeek]

in my side it is also crashing and terminal shows

/Applications/BitBox.app/Contents/MacOS/BitBox ; exit;
SingleApplication: Unable to create block.
SingleApplication:  7 "QSharedMemory::create: out of resources"

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...      36 completed.

[Process completed]

[marc-cgn]

Conclusion: THERE IS A SERIOUS SHARED MEMORY PROBLEM in the bitbox app. I strongly recommend to transcode the app to native Silicon ARM code or to at least make the app a UNIBVERSAL code app having both codeworks included.

PLease: FEEDBACK: URGENTLY

Also total unhappy, that bitbox is ignoring Apple Silicon for years now. This *****y framework is not working properly and just a nightmare.