Describe the bug
Zingo crashes immediately on every launch attempt on macOS. The app is installed via the App Store as the iOS build running under Mac's "Designed for iPad"/iOS-app compatibility layer (confirmed via bundle structure: /Applications/Zingo.app/Wrapper/Zingo.app/, FairPlay-DRM'd binary). It terminates with SIGABRT (abort() called) within ~3 seconds of launch, every time, with no error shown. The app just disappears.
Crash reports show the abort is called deliberately from Zingo's own code on a background dispatch queue (com.apple.root.user-initiated-qos), not from a memory-safety fault, an OS kill, or the main UI thread. This looks like a failed startup precondition check (e.g. a local data/database read, decrypt step, or migration check) that calls abort() instead of surfacing an error.
To Reproduce
- Launch Zingo normally from Launchpad/Finder on macOS (Apple Silicon)
- App opens briefly then closes immediately
- Repeated on 3+ separate launch attempts, same result every time
Expected behavior
App should launch normally, or at minimum show a recoverable error instead of a silent abort — especially given this may involve a local wallet-data read failure.
Desktop:
- OS: macOS 26.6.1 (build 25G76)
- Hardware: Mac15,6 (Apple Silicon)
- App: Zingo (iOS build via Mac compatibility layer, not native zingo-pc)
- Version: 2.0.22 (build 313)
Additional context
- Crash type: EXC_CRASH (SIGABRT), Termination Reason: SIGNAL/6/Abort trap: 6
- Crashing thread (Thread 9 in report) stack: __pthread_kill → pthread_kill → abort → [Zingo internal frames, unsymbolicated] → _dispatch_call_block_and_release → _dispatch_client_callout → _dispatch_root_queue_drain → _dispatch_worker_thread2
- Full symbolized Console.app crash report available and can be attached/pasted on request — includes readable Hermes/React Native frames for the main thread and the aborting background thread
- I have not reinstalled, deleted, or otherwise modified the app or its local data, to avoid risking loss of wallet access. I would appreciate guidance on:
- Whether this crash pattern is likely to involve corrupted/inaccessible wallet data, or purely a UI/runtime-layer issue
- Whether zingo-cli's --recover flag (mentioned in zingolib) is applicable here, and if so, where the Mac App Store build's wallet data directory is actually located
- Any safe way to export the seed phrase without a full successful app launch
Happy to provide the full crash log (.ips and/or symbolized Console report) on request.
Describe the bug
Zingo crashes immediately on every launch attempt on macOS. The app is installed via the App Store as the iOS build running under Mac's "Designed for iPad"/iOS-app compatibility layer (confirmed via bundle structure: /Applications/Zingo.app/Wrapper/Zingo.app/, FairPlay-DRM'd binary). It terminates with SIGABRT (abort() called) within ~3 seconds of launch, every time, with no error shown. The app just disappears.
Crash reports show the abort is called deliberately from Zingo's own code on a background dispatch queue (com.apple.root.user-initiated-qos), not from a memory-safety fault, an OS kill, or the main UI thread. This looks like a failed startup precondition check (e.g. a local data/database read, decrypt step, or migration check) that calls abort() instead of surfacing an error.
To Reproduce
Expected behavior
App should launch normally, or at minimum show a recoverable error instead of a silent abort — especially given this may involve a local wallet-data read failure.
Desktop:
Additional context
Happy to provide the full crash log (.ips and/or symbolized Console report) on request.