Thanks, I’ve already gone through the technical note, but it lacks more detailed information regarding the fallback mechanism you mentioned. "3. If none of the user’s preferred languages are supported by your app, iOS chooses the language matching your app's development region (CFBundleDevelopmentRegion)." In my opinion, this is misleading. As I understand it, the system should default to the CFBundleDevelopmentRegion, but we also know that there’s a linguistic decision involved in addition.

"the system uses a linguistic fallback tree to find the closest possible match among the languages your app actually supports." It seems like a correct behavior for most cases. However, in my situation, I require a direct fallback mechanism when there’s no precise match between the system’s preferred languages and the languages supported by the app. As you mentioned, I need to handle this manually. Could you provide me with some guidance on how to implement this please?

Thanks, it helps to get over it, but it's annoying because you have to do it each time you start Xcode. I had this issue in previous versions of macOS as well; it can be resolved by changing the audio output for the running simulator. This is not the case in macOS Tahoe.