So it turned out, in that case settings.authorizationStatus is set to .provisional and not .authorized.

My bad—it turned out I was using my iPad in zoomed mode 🙈 and that is why there was difference in how things were displayed during the tests and on my device.

By device frame I mean the metallic frame with the buttons etc. It is sometimes called "bezel". Please see the attached image. I ended up doing it semi-manually in Figma. I had screenshots exported automatically for all devices and languages by Xcode UI tests. Then I just added the frame to every screenshot manually. @Claude31 I can highly recommend investing some time in making UI test generate screenshots for you so that screenshots capture: any new changes any new language added any new devices you need screenshots for

I received an answer from AWS support and the issue has been resolved. It turned out that the problem was related to the nameservers. My domain is hosted on AWS, but my backend is in Google Cloud. While configuring my backend I must have changed the default nameservers on AWS to the ones provided by Google: ns-cloud-c1.googledomains.com. ns-cloud-c2.googledomains.com. ns-cloud-c3.googledomains.com. ns-cloud-c4.googledomains.com. The AWS support advised me to switch back to the default ones provided by AWS, because they were specified by whois lookup: ns-1553.awsdns-02.co.uk ns-857.awsdns-43.net ns-91.awsdns-11.com ns-1160.awsdns-17.org One of the beta testers, who previously experienced connection problems, reported that he was able to use the app on WiFi without any problems. As a side note, I have also been shown a handy tool to inspect how different locations resolve an IP address of a domain: https://www.whatsmydns.net/#NS/apple.com FYI @eskimo and thanks again for your input!