NativeScript iOS Daily: Worker Overhaul and a Suspended-App Crash Fix
This cycle reshaped how worker options are structured and controlled, while fixing a production crash tied to iOS suspending apps, and tightened the embedder API's contract with Swift.
Duration: PT2M14S
Episode overview
This episode is a short developer briefing from NativeScript iOS Daily.
It explains recent repository work in plain language.
- Show: NativeScript iOS Daily
- Published: 2026-09-07T13:10:50Z
- Audio duration: PT2M14S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day. It's September 7th, 2026, and this is NativeScript iOS Daily.
The top story: workers got a real API redesign, and a serious crash affecting suspended apps got fixed at the root.
Start with workers. PR 470 introduces an "ios" namespace for platform-specific worker options, replacing the old "iosPriority" flag, which is now deprecated but still functional with a one-time warning. Building on that, PR 471 adds Node-style resource limits, letting developers cap a worker's old and young heap…
Second theme: runtime lifetime safety. PR 469 fixes a crash where iOS calls exit() on a background thread while suspending an app, which was tearing down the V8 platform and the main runtime out from under still-running workers. The fix makes both long-lived globals raw pointers that survive exit(), deleted only…
Third, smaller but relevant: PR 461 adds nullability annotations to NativeScript-dot-h, so Swift embedders see accurate optional versus required pointers instead of implicitly unwrapped ones. It also fixed a related bug where a nil arguments array with a stale count could index into null.
What to remember: if you're using workers, migrate off iosPriority toward the ios options…
Nearby episodes from NativeScript iOS Daily
- Worker API Gets a Redesign, Plus a Suspend-State Crash Fix
- Runtime Startup Crash Fixes
- Closing the Worker Memory-Corruption Hunt
- Worker Threads Land, Then Get Hardened
- Web Globals Land, Memory Leaks Get Squashed
- The Runtime Goes Web-Standard
- Loader Hardening Closes Out
- Hot Module Loading Meets Strict Validation