Skip to content

Conversation

@ryanbooker
Copy link

@ryanbooker ryanbooker commented Oct 31, 2025

On Xcode 26 we found that iOS 15 release builds started crashing when resolving interpolated localised strings. This turned out to be related to the generated overrideKeyForLookup. Changing from assumingMemoryRebound to withMemoryRebound fixes the crash and doesn't seem to have any unexpected side effects. The strings still resolve to the expected values.

This PR implements that fix.

However we also wondered if there is an alternative, for example while the generated LocalizedStringKey.localizable path ends up in the overrideKeyForLookup method on iOS 15, the String.localizable path does not. Is there a way to use the more direct and safer path from String.localizable?

In any event this PR should fix the issue we were experiencing.

Please let me know if you need anything from us. We do have a tiny example project illustrating the issue if you'd like to see it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant