Post

Replies

Boosts

Views

Activity

Reply to App Store Connect: Can't change Primary Locale to nl-NL — 19 historical versions blocked by missing screenshots, API returns 409
I think that's expected in my case. From what I can tell those Root.strings inside each .lproj belong to a Settings.bundle, which localizes the app's pane in iOS Settings.app. We don't ship a Settings bundle (Expo doesn't generate one by default), so the only thing in our en.lproj / nl.lproj is InfoPlist.strings, which is what the CFBundleLocalizations change produced. I did rebuild and re-upload with the localization config in place, and App Store Connect still rejects the primary locale change with the same error, so I don't think the binary side is what's being validated here. Coming back to the original issue: the 409 is MISSING_SCREENSHOTS_PRIMARY_LOCALE raised against historical appStoreVersions (19 of our 23 versions have an nl-NL localization with description and keywords, but no screenshots attached). Those versions are locked against edits at the API level too, not just in the UI, so there's no interface I can use to attach screenshots to them. That looks like metadata state that no new build can change.
Aug ’26
Reply to App Store Connect: Can't change Primary Locale to nl-NL — 19 historical versions blocked by missing screenshots, API returns 409
@Claude31 @Frameworks EngineerThanks for putting those ideas out there :D When we took over the app it had English and German, so I wanted to add dutch and make it the primary language since the app is only available in Dutch and English. I've checked the other languages and made sure that we have media for all of them on the highest resolution display This was something I was not aware of, we use Expo, so what I did was add some lines to the app.config that would then later generate the nl.lproj file. I will try this new bundle later, and I will follow-up on this with you. { locales: { en: './locales/en.json', nl: './locales/nl.json' }, build: { .... infoPlist: { CFBundleLocalizations: ['en', 'nl'], CFBundleAllowMixedLocalizations: true } } I've tried to do it from the other languages and nothing helped there.
Aug ’26
Reply to App Store Connect: Can't change Primary Locale to nl-NL — 19 historical versions blocked by missing screenshots, API returns 409
I think that's expected in my case. From what I can tell those Root.strings inside each .lproj belong to a Settings.bundle, which localizes the app's pane in iOS Settings.app. We don't ship a Settings bundle (Expo doesn't generate one by default), so the only thing in our en.lproj / nl.lproj is InfoPlist.strings, which is what the CFBundleLocalizations change produced. I did rebuild and re-upload with the localization config in place, and App Store Connect still rejects the primary locale change with the same error, so I don't think the binary side is what's being validated here. Coming back to the original issue: the 409 is MISSING_SCREENSHOTS_PRIMARY_LOCALE raised against historical appStoreVersions (19 of our 23 versions have an nl-NL localization with description and keywords, but no screenshots attached). Those versions are locked against edits at the API level too, not just in the UI, so there's no interface I can use to attach screenshots to them. That looks like metadata state that no new build can change.
Replies
Boosts
Views
Activity
Aug ’26
Reply to App Store Connect: Can't change Primary Locale to nl-NL — 19 historical versions blocked by missing screenshots, API returns 409
@Claude31 @Frameworks EngineerThanks for putting those ideas out there :D When we took over the app it had English and German, so I wanted to add dutch and make it the primary language since the app is only available in Dutch and English. I've checked the other languages and made sure that we have media for all of them on the highest resolution display This was something I was not aware of, we use Expo, so what I did was add some lines to the app.config that would then later generate the nl.lproj file. I will try this new bundle later, and I will follow-up on this with you. { locales: { en: './locales/en.json', nl: './locales/nl.json' }, build: { .... infoPlist: { CFBundleLocalizations: ['en', 'nl'], CFBundleAllowMixedLocalizations: true } } I've tried to do it from the other languages and nothing helped there.
Replies
Boosts
Views
Activity
Aug ’26