NativeScript iOS Daily: The String Bridge Overhaul
A single large merge from Eduardo Speroni rewrote how text moves between V8 and Objective-C, cutting conversion costs by up to eight times while fixing several silent data-loss bugs; two smaller commits patched a napi context bug and pinned a V8 build to restore public API exports.
Duration: PT2M19S
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-08-14T13:14:15Z
- Audio duration: PT2M19S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, and welcome to NativeScript iOS Daily for August 14th, 2026.
Today's biggest story is one theme: string conversion across the JavaScript and Objective-C bridge was quietly expensive and, in edge cases, quietly wrong. PR 442 fixes both problems at once.
The core insight: V8 and CFString already store text in compatible native formats — Latin-1 or UTF-16 on both sides. But the runtime was routing conversions through UTF-8 anyway, paying for an encode, a decode, and an allocation just to move data between two shapes that already matched. Commit b-f-c-6-c-5-e shows…
This wasn't just a performance pass. The old UTF-8 path had real bugs: a lone surrogate in a string would silently turn into an empty string crossing from JavaScript to native and back. Exception messages, error descriptions, and selector names all got hardened as part of the same effort. One standout: the unichar…
Two smaller, unrelated fixes round out the day. Commit 3-6-4-5-8-9-8 addresses a napi threading bug: async work completion wasn't entering the environment's context, so exception reporting and completion callbacks ran blind — mirrored from a similar fix already shipped on Android. And commit…
What to…