Given that Apple is a Sponsor level member of the FIRa Consortium (on UWB interoperability) and the FIRa 3.0 spec has been released, are there any improvements in the Nearby Interaction framework for UWB direction tracking? It appears that NI returns null for direction-found with third-party UWB device currently.

using String Catalog, missing locale entries don't fall back to source language. for example, "%lld videos" : { "comment" : "Label for a number of videos", "extractionState" : "manual", "localizations" : { "en" : { "variations" : { "plural" : { "one" : { "stringUnit" : { "state" : "translated", "value" : "%(count)lld video" } }, "other" : { "stringUnit" : { "state" : "translated", "value" : "%(count)lld videos" } } } } }, this allows us to use Text(.videos(count: 1)) in English and it'll produce "1 video" as expected but when the locale is French for example, it'll produce "1" instead, until "fr" entry will be added. this is extremely inconvenient. what's the proper workaround?

I have a large dictionary of words in an app that I’d like to localize. I'm thinking of asking a human translator (or AI agent) to translate them. I might translate each word by machine and include the translation in the data I provide to the translator as candidates. How can I export this data to the translator in XLIFF format? Does iOS have API for XLIFF generation or interpretation? Are there decent open source options written in Swift?

Our app lets users pick the locale for a particular document (macOS document-based AppKit), then produce outputs using various inputs (user-provided and others) in that locale. We've written much of the plumbing, but are getting really close to String Catalogs and the like. What can we do to use AppKit and Xcode's localization tools correctly and efficiently in this case? We already have "Localization" objects, and are splitting the work into multiple String Catalogs for clarity. In each case the app will need to use the given Localization to produce (or replace) text at runtime, including the result of formatters

Is there documentation or a video for -[NSString initWithValidatedFormat:validFormatSpecifiers:locale:error:] and similar APIs?

I'm amazed by agentic coding presented in the "Translate your app using agents in Xcode" session. Does agentic translation support localized strings contained in Objective-C modules? Does it support strings in Interface Builder XIBs?

Hi, thanks for offering this Q&A! We've always used real translators for our apps, but recently our vendor went out of business, and this WWDC is focusing heavily on agentic localization. It's clear this is where the industry is trending, but we're worried about our user experience if we have a fully AI-driven localization. How do you recommend verifying that agentic localization output is correct, friendly, appropriate, etc?