Sounds like the same issue discussed in this thread.

Ah, so this is only on TestFlight? Could be due to the yellow dot in front of the label. That reduces the available space and could conceivably trigger different shrinking logic. Unfortunately there’s nothing you can do about that, and the same thing will happen when there’s a blue dot after an app update. In fact, now I can get the perfect removal of the space with simple labels of * Toronto Hydro, - Toronto Hydro, and • Toronto Hydro. I think your label text just happens to be just right to trigger this effect when a marker character is prepended.

Are you sure this isn’t just the behavior where iOS tries to squeeze whitespace to make the label fit without truncation? That’s based on the actual size of the text on screen rather than the length in characters. That said, I tried display name Toronto Hydro on a few different simulators here and it seems ok. The space does get squished a bit on the iPhone SE (1st gen.) but looks normal on larger simulated devices. Are you seeing this problem on all display sizes and all iOS versions? A couple sanity checks would be to: Test with simple cases such as A B and iiii iiii iiii. Test outside your app by making a Home Screen folder, and then manually rename it to Toronto Hydro. I believe folder labels should render exactly the same as app display name. Any difference?

The review guidelines wouldn't specifically mention disallowing reading the phone number because there’s no public API for reading the phone number in the first place. Anything that’s impossible using public APIs is implicitly disallowed.

Asking here in the forum is proof that the documentation isn’t exactly complete. But we may be able to infer clues from the equivalent newer async method upload(for:from:delegate:). That method either returns a (Data, URLResponse) tuple or throws an error, so we know you’ll never get data or a response in the case of an error. And note the return tuple’s URLResponse is non-optional, so it will always be present if no error. The tuple’s Data is also non-optional but could be empty, so we can’t say for sure if that’s the case in the old version of the method. Probably best to handle both a nil data and an empty data the same way.

Not possible; see this for details.

In addition to accessibility settings, note there’s a global Display Zoom toggle in the Display & Brightness settings (on device) and in the Developer settings (on simulator).

The error message means the storyboard is looking for an outlet named saveNotes but your code shows that the outlet is named saveNote.

I think most developers would consider 8 GB of RAM too small. Try to get 16 GB at minimum, preferably 32 GB.

Are you looking for the device bezel (picture of the physical device) around the display? Simulator doesn’t save that. “Device mask” refers to the rounded corners and the top notch on devices without a home button. Saving with that option renders those areas transparent.