Use Xcode’s Double-Length Pseudolanguage to find views that depend on short English labels. It gives you a repeatable way to expose layout failures early.
Run a narrow-screen test
Choose Product → Scheme → Edit Scheme, then Run → Options. Under App Language select Double-Length Pseudolanguage. Open a screen with a long label beside its primary button on a narrow simulator. Check whether the label wraps, truncates, or pushes the button away.
Fix the layout and retest
If the label crowds the button, try allowing the label to wrap or stacking controls vertically when space runs out. Repeat the same test and check that the full label is readable and the action is reachable. Then run the real languages you support. Pseudolanguage exposes some layout assumptions, while native-language tests cover real copy and writing conventions.
Pick a specific failure condition before opening the simulator. On a checkout screen, for example, the order total and the Continue button must remain readable and reachable even when the label grows. Capture the original layout and the expanded layout on the same simulator. If the issue happens only when two controls share a row, isolate that row before changing the rest of the screen.
Then try a second stress test. A larger text size can expose a different problem, such as wrapping increasing the screen height while the button still has to remain reachable. A right-to-left pseudolanguage can help you spot controls that stay on the wrong side, while real translations will also exercise wording, punctuation and fonts. Keep a short checklist of the labels and actions that must remain visible, and rerun it on the smallest screen your app supports.
https://developer.apple.com/documentation/xcode/preparing-your-interface-for-localization