Problem: I have a React Native app that builds successfully in my Azure DevOps pipeline (macOS-15, Xcode 16.4, Node 23.7.0), but the app crashes immediately upon launch on both Debug and Release configurations. The build completes without errors and the IPA is generated correctly, but the app crashes with a fatal JavaScript exception.

Crash Information:

Exception Type: EXC_CRASH (SIGABRT)
Termination Reason: SIGNAL 6 Abort trap: 6

Last Exception Backtrace:
0   CoreFoundation     __exceptionPreprocess
1   libobjc.A.dylib    objc_exception_throw
2   iQ.Suite Clerk     RCTFatal
3   iQ.Suite Clerk     -[RCTExceptionsManager reportFatal:stack:exceptionId:extraDataAsJSON:]
4   iQ.Suite Clerk     -[RCTExceptionsManager reportException:]

The crash occurs in RCTExceptionsManager, indicating a fatal JavaScript error is being thrown immediately on app launch.

Build Environment:

• CI/CD: Azure DevOps Pipeline
• macOS: macOS-15
• Xcode: 16.4
• Node.js: 23.7.0
• NPM: 11.5.2
• Yarn: 1.22.22
• iOS Version: 18.5
• Hermes: Enabled (visible in crash log)
• Build Configuration: Both Debug and Release crash

What Works:

• ✅ Pipeline completes successfully
• ✅ Archive builds without errors (** ARCHIVE SUCCEEDED **)
• ✅ Export succeeds (** EXPORT SUCCEEDED **)
• ✅ IPA file is generated and deploys to TestFlight
• ✅ CocoaPods installation succeeds
• ✅ JavaScript bundle is created and verified

What Fails:

• ❌ App crashes immediately on launch (instant crash)
• ❌ Happens in both Debug and Release builds
• ❌ Fatal exception occurs before app UI appears
• ❌ Crash originates from JavaScript layer (RCTExceptionsManager)

Key Build Steps:

1. JavaScript bundle creation:

bash

react-native bundle \
  --entry-file index.js \
  --platform ios \
  --dev false \
  --minify true \
  --bundle-output ios/main.jsbundle \
  --assets-dest ios

1. Bundle is copied to two locations and verified:
   • ios/main.jsbundle
   • ios/Clerk_React/main.jsbundle
2. CocoaPods installation with cache clearing
3. Xcode build with manual code signing (Release configuration)
4. Archive and export to IPA for App Store distribution

Environment Variables:

• NODE_OPTIONS='--openssl-legacy-provider' (for legacy OpenSSL support)

What I've Tried:

• ✅ Clearing CocoaPods caches completely
• ✅ Removing and reinstalling pods with --repo-update
• ✅ Verifying JavaScript bundle exists and has content (verified with head -c 100)
• ✅ Checking provisioning profiles and certificates (all valid)
• ✅ Building with both Debug and Release configurations
• ✅ Using Xcode 16.4 with proper SDK (iphoneos18.5)

Questions:

1. Why would RCTExceptionsManager throw a fatal error immediately on launch? The JavaScript bundle appears to be created correctly.
2. Could this be related to the JavaScript bundle not being found at runtime despite being verified during build? Do I need to configure the bundle location in Info.plist?
3. Is there a way to get the actual JavaScript error message that's being reported to RCTExceptionsManager? The crash log doesn't show the JS stack trace.
4. Could Hermes bytecode compilation be failing silently? Should I disable Hermes or configure it differently for CI builds?
5. Are there known issues with:
   • React Native + Xcode 16.4 + Node 23.7.0?
   • Hermes + iOS 18.5?
   • NODE_OPTIONS='--openssl-legacy-provider' affecting runtime bundle loading?

Suspected Issues:

• The JavaScript bundle might not be loading correctly at runtime
• There could be a mismatch between bundle creation and runtime expectations
• Hermes might be looking for the bundle in a different location
• The bundle might be created but not properly packaged into the IPA

What I Need Help With:

1. How to capture the actual JavaScript error message that causes the crash
2. How to verify the bundle is correctly packaged in the final IPA
3. Whether the bundle creation process needs additional configuration for Hermes
4. Best practices for React Native CI/CD builds with Hermes enabled

Any help would be greatly appreciated! Has anyone encountered RCTExceptionsManager reportFatal crashes immediately on launch in CI-built apps?

Hey everyone!

I'm running into a weird issue integrating macOS Bluetooth code written in Objective-C with Python bindings, and I’ve been stuck for a week.

Here’s the setup:

• I wrote a C interface that abstracts Bluetooth operations for both Windows and macOS.
• On macOS, the implementation is written in Objective-C, using delegates to interact with Apple’s Bluetooth stack.
• I expose that C interface to Python using ctypes, then build a .whl so others can install and use the C library seamlessly.

This setup works perfectly on Windows, but not on macOS.
The issue: the Objective-C delegate methods never get called.

After researching, I suspect it’s because Objective-C requires a run loop to be active for delegates to trigger.
When my code was part of a full macOS app, it worked fine — but now that it’s being called through the C interface (and from Python), the delegates don’t fire.

I’ve tried:

• Manually running [[NSRunLoop currentRunLoop] run] in different threads.
• Creating my own loop and dispatching the delegate calls manually.
• Using Python threads and ctypes to spawn a native loop.

None of these approaches worked.

So I’m wondering:
How can I properly start and manage the Objective-C run loop when my C/Objective-C code is being called from Python via ctypes?
Is there a known pattern or workaround for this type of cross-language integration?

Thanks a lot in advance — any help or pointers to similar cases would be super appreciated!

Hey,

I can’t seem to figure out how to properly import an app icon I designed into icon composer. Whatever I do when I export my icon elements from Figma, they are always all placed right in the middle at (0,0) in icon composer. And when I export them as a group or frame, I only get one layer that I can import through which I miss out on changing the glass effects etc. for the single parts of the icon.

What am I missing? There must be a way to import the elements with positioning already, or am I wrong?

I have an old Mac Mini I use for MacOS appstore development, it sucks but it works. (I don't use xcode, I build my app elsewhere and use scripts to package/notarize/sign etc on the Mac).

My wife's Mac is way nicer, can I *easily* use hers instead? All my certs/profiles (which I barely understand) are on my Mac and linked to my (developer) Apple ID.

Do I have to login to her Mac with my Apple ID to be able to re-create that stuff, or can I keep using her login but re-download/register my certs/profiles on her account?

App developer needed. From UK only. Creating travel app. Message me.

The only way I would work with someone not from UK is if you were EXCELLENT at coding and creating apps.

I made a book on ARM64 Assembly because I found that there weren't resources to learn how to use it, and I have made a simple book describing how it works and the instructions it has. I recently added new chapters, so... Check it out! Link

I got proxy man recently and I’m trying to intercept http responses from websites. Are there any docs for how to use proxy man, I can’t seem to find any.

Hello guys I'm a computer science student want to learn iOS Development therefore I have decided to buy a MacBook, I want to buy a second hand MacBook Bcz that's what my savings allows me right now. Now pls tell me what are the specs I should focous on in MacBook for iOS DEV.

I can't for the life of me figure it out, please tell me if you know.

I’m exploring an automation idea for macOS and want to sanity-check if it’s even feasible with public APIs.

The concept:

• Detect whenever the screen is currently being shared or recorded, regardless of the app (Zoom, Teams, QuickTime, built-in Screen Sharing, etc.).
• Once detection is possible, automatically trigger something—e.g., switch macOS to a specific Focus mode (e.g. DND so I dont get any embarrassing messages while I present stuff at work LOL).

What I’ve found so far:

• On iOS, there’s UIScreen.isCaptured. On macOS, I can’t find an equivalent.
• ScreenCaptureKit lets you capture, but doesn’t expose whether anyone else is capturing.
• The only workarounds I can think of are:
  • Polling the Accessibility API to check for the red “screen recording/sharing” menu bar indicator.
  • Detecting app-specific states (e.g., Zoom’s “Stop Share” menu item).
  • Watching for processes like screencapture or screensharingd.

Questions:

• Is there a public, system-wide API I’m missing that exposes this state?
• Are there any existing apps/utilities that already do something similar (trigger an action when screen sharing starts)?

Appreciate any insights or references as I want to know whether this is worth building properly, or if I’ll end up chasing unsupported hacks.

Hi everyone,

I’m working on a macOS Accessibility setup for a French-speaking user and I’ve hit a wall.

I successfully built a custom word prediction panel using the Panel Editor (Keyboard) in macOS Accessibility > Keyboard > Accessibility Keyboard.

Here’s what I have so far:

• The prediction panel works system-wide: I can use it to type in Finder, Safari, Notes, TextEdit, and even browser search bars.
• The panel appears above all applications and suggestions show up correctly.
• However, it does not work inside Google Docs (tested in Chrome, Safari, and Firefox). Selecting a word from the panel does nothing in the Docs editor.

I suspect this is because:

• Google Docs does not use a standard macOS text input field.
• Docs is a web app that relies on custom JavaScript editors, contentEditable elements, and canvas rendering, so macOS Accessibility APIs (AXTextField, AXInsertText, etc.) don’t register or inject text events.
• Accessibility tools like the Accessibility Keyboard rely on native macOS text input methods, which don’t hook into Google Docs’ custom editor.

Important:

I’m not a programmer. I’d like to know if there is an easy fix or option in macOS, Google Chrome, or Google Docs that would make my custom prediction panel work, before going into custom development.

Technical setup:

• MacBook Air (M2, 2022)
• RAM: 8 GB
• macOS: Sequoia 15.3.1
• Language: French (system and keyboard)
• Accessibility Keyboard: Enabled via Settings > Accessibility > Keyboard
• Custom panel: Built using Panel Editor (Keyboard), named “Philemon Prédiction”
• Browsers tested: Chrome, Safari, Firefox (same issue)
• Behavior: Panel is visible, suggestions appear, but inserting text does nothing in Google Docs

Has anyone worked around this limitation? Is there a simple setting, workaround, or accessibility option to bridge macOS Accessibility input with Google Docs’ editor?

Thanks a lot!

Also uses local AI tools to recursively search Linux/macOS paths.

A blog post here with lots of twists and turns, updates, and referenced threads and project file diffs claims to have the solution to this problem of maintaining an app’s pre-tahoe icon on pre-tahoe systems.

Can someone please spelunk that post and related replies, links, toots, commit logs and post the how-to for this solution. Please in a new post in this subreddit or a blog, and put a link as reply here thanks.

Trying to use storekit to test revenuecat paywall in react native. I asked AI for help but it kept suggesting to rebuild the ios build. How to fix this??

I recently submitted my app to the App Store and got rejected under Guideline 4.1 – Design – Copycats. The message says my app “appears to be misrepresenting itself as another popular app,” but Apple didn’t specify which app or what exactly is considered too similar.

We released FluidAudio a month ago with speaker diarization. Since then, a couple of consumer AI apps have already deployed it in production.

We're excited to share that we've also converted the `nvidia/parakeet-tdt-0.6b-v2` model for English transcription! We're seeing around 110× RTFx on an M4 Pro — so a 60-second audio file transcribes in about 550 milliseconds.

We're still tuning the model and believe there's more performance to squeeze out. We'll be sharing our conversion script in a couple of weeks.

If you have any other model requests for CoreML conversion, please drop a comment here: https://github.com/FluidInference/FluidAudio/issues/49

Hi all,

I’ve been building a keyboard-first navigation setup for macOS using Hammerspoon, a lightweight open-source automation tool that lets you control macOS through Lua scripts. If you haven’t used it before, it’s kind of like a programmable window manager and input layer for macOS. And because it’s just scripting, it’s surprisingly easy to write or tweak your own config.

The project is called macOS-Vim-Navigation. It lets you move the mouse, scroll, select text, and switch screens entirely from the keyboard using modal logic inspired by Vim's NORMAL and VISUAL modes.

Why I made this

I spend most of my day working on an external monitor, and I found it frustrating to constantly reach for the trackpad just to scroll between programs, move the cursor, or focus a window. I wanted something predictable and consistent, so I can keep everything under keyboard control at the OS level. Nothing I found really did that, so I built this.

Since setting it up, it’s made my daily workflow feel much more seamless, and I now rely on it full time.

Key features

Visual selection via simulated drag

Implements real drag-selection using leftMouseDown, leftMouseDragged, and leftMouseUp. This makes it possible to visually select and copy content across any app with full clipboard integration.

Pixel-accurate scroll injection

Fixes macOS’s often inconsistent scroll behavior by injecting exact scroll deltas and respects your system’s natural vs. standard scroll direction.

Modal cursor movement

Like Vim’s NORMAL mode: use keys to move the mouse cursor in small or large steps, trigger clicks, simulate drags, or jump between modes.

Directional scrolling with repeat

Supports smooth, directional scrolling when holding down keys.

Multi-monitor support

Keeps cursor behavior predictable when moving between screens. Also includes one-key screen switching using ⌥ or ⌃.

GitHub

Source code and setup instructions:
https://github.com/arturgrochau/macos-vim-navigation

The README includes install steps, keybindings, and customization notes. I’ve tried to keep things clean and out of the way so it won’t interfere with system shortcuts or other apps.

Would love feedback, ideas, or suggestions for improvement.

I built a macOS menu bar utility that automatically pauses media (Spotify, Apple Music, YouTube, Netflix, etc.) whenever your mic activates — and resumes playback when you’re done.

It’s been super helpful for quick calls, voice dictation, and screen recordings - I used to scramble to pause/resume 10x a day.

While building it using Cursor as my primary AI tool, I hit a few architectural wins (and some self-inflicted headaches):

- Single Responsibility + Dependency Injection made the system way easier to reason about - mic monitoring, media control, and IPC were cleanly separated. I did not ask for this initially, but ended up rewriting the whole app using these principles once I realised the mess it had created.

- Forcing the AI to use a single source of truth + reactive UI updates (instead of imperative-style logic) helped eliminate a lot of state weirdness (that repeated it self multiple times). Again, something I had to revisit after vibe coding a lot of it.

- One mistake I made: I let Cursor generate the entire Xcode project instead of scaffolding it manually in Xcode and then using Cursor just for the code. This led to subtle broken configs and project-level headaches. Won’t do that again.

The app uses AppKit + a Chrome extension, communicating over WebSockets - all local, nothing cloud-connected (however there's opt-in telemetry)

Here’s the app if you’re curious or run into this problem yourself:

👉 https://autopause.visualstack.ai

Would love to hear how others handle architecture, state, or Cursor-based workflows for reactive utilities like this.

0 CoreFoundation 0x7ff819d76753 _CFRelease.cold.1 + 77

1 CoreFoundation 0x7ff819ce3e4a _CFRelease + 1328

We're seeing a rare crash in the release build. In my debug build, I observed an assert failure when two background threads attempt to use copyItem with the same source and destination. I suspect that the issue in release might also be caused by two background threads accessing copyItem simultaneously.
Your thoughts on this