I've raised a feedback message for this: FB7537885

I have the same status: "Potential fix identified - For a future OS update"

In case anyone else is interested, I got around this by using the 13.2.2 simulator in my UI tests.You can have multiple schemes and tick which tests to run, so if you have a subset of tests that need 13.2.2, you can tick the tests to run in that scheme only (and untick them in the other scheme) - then if you've got a CI / buld server with a script calling xcodebuild you can specify the different scheme and different simulator version, something lke:-scheme "ui-tests-only-for-13.2.2" -destination "platform=iOS Simulator,name=iPhone 11,OS=13.2.2"We're just using 13.2.2 for all our tests - but that above is (possibly) a workaround if you need to split out tests on a build server for iOS 13.3 specifically (depends if you're not bothered about testing other features of SFSafariViewController on 13.3 though!)We plan on doing this until we need something specific about iOS 13.3 for SFSafariViewController.Fingers crossed Apple will sort it out for iOS 14 😉

Use case: I'm using the following String extension to change the language/locale in the Swift UI environment, I then pass the locale through to the function to get a localised string. I've made a little Swift UI preview container with an editor panel so we can toggle values in the environment (dark mode, layout direction, locale/language etc) on previews and also within a playbook app - without needing to select a drop-down in the Xcode scheme editor and restarting the app, or needing to change the device settings (although we have to do that when running on iOS 15.) func localized(_ locale: Locale, bundle: Bundle = .module) -> String { if #available(iOS 16, *) { String( localized: LocalizedStringResource( String.LocalizationValue(self), locale: locale, bundle: .atURL(bundle.bundleURL) ) ) } else { String(localized: String.LocalizationValue(self), bundle: bundle) } }