Open Radar

 
When using the iOS localization mechanism, an empty translation for a given key will result in the key itself being rendered in a SwiftUI Text() structure.

Given the following Localizable.strings:
“test1” = “foo”;
“test2” = “”;

And the following SwiftUI code:
VStack {
    Text(“test1”)
    Text(“test2”)
    Text(“test3”)
}

The expected output is:
foo

test3

Explanation:
foo – correct translation for “test1”
<empty> – correct translation for “test2”
test3 – no translation available so correct fallback for “test3”

Actual output:
foo
test2
test3

In this, the “test2” is unexpected, because a translation has been provided for that key.

This is reproducible on iOS 14.5 and 15.0 in the simulator, and in 15.1 on a real device. However, this appears to not have been an issue on a real device running 14.8.

Happy to provide any more necessary information.