Lately I am getting this error.
GenerativeModelsAvailability.Parameters: Initialized with invalid language code: en-GB. Expected to receive two-letter ISO 639 code. e.g. 'zh' or 'en'. Falling back to: en
Does anyone know what this is and how it can be resolved. The error does not crash the app
Does the error appear in the console, or is it being thrown when you attempt to call respond(to:)?
I experience the same issue. First time I saw this error was when I installed XCode 26.0.1 I suspect this is a bug in Xcode as the error seems to relate to something in different framework.
Hi all!
If you see this issue, first verify that your Mac and Xcode are on the exact same version, e.g, 26.2. Some of these kind of strange errors can come up due to version mis-match.
If that does not resolve the issue, please file a Feedback Assistant report.
Thanks!
Same here.
-[AFPreferences _languageCodeWithFallback:] No language code saved, but Assistant is enabled - returning: fr-FR
GenerativeModelsAvailability.Parameters: Initialized with invalid language code: fr-FR. Expected to receive two-letter ISO 639 code. e.g. 'zh' or 'en'. Falling back to: fr
Mac is 15.7.3
Xcode is 16.4.
Yes, I know, I'll have to update soon.
I'm getting these:
[AFPreferences _languageCodeWithFallback:] No language code saved, but Assistant is enabled - returning: en-AU
messages when debugging a SpriteKit app within the simulator.
Now admittedly, I am running macOS 15.8 (24H23) and Xcode Version 26.3 (17C529) so yes there is a delta.
But what I'm trying to understand is why does that matter, and why, when I do see this in the console, does the touch on the simulator get ignored?
What is actually going on here? I should be able to debug within the iOS simulator without this sort of thing happening. I'm not using any AI stuff within my app, and have not turned anything on nor logged into iCloud within the simulated device.
I should also note that I see this same issue even for the macOS target running natively on the Mac, so it is not purely related to the simulator.
For iOS, I guess I can try running on a physical device to see if the problem goes away there, but to my mind the simulator should be a true representation of the real device. Otherwise, how would one ever test for Vision or Duo, as those devices are far too expensive to own.