“show when run”

Hello @kai_, Your sample code uses a standard font which will adapt to the users selected font size. iOS provides a wide range of text sizes for the user to select from. Build your app to be accessible to users who select a different text size. For more information see Typography and Font. When I run your code on an iPhone 15 with 26.4, I can see the full text. It seems the size of the text in your environment does not fit within its content margins. To see these margins, try using Xcode's Debug View Hierarchy feature. Take look at these margins and resource, let me know what you find.  Travis

I worked around this by running the command line app using launchctl asuser 501 xxx

Thank you. I did not think MAC was any different (latest MAC that is). That is because I managed to install my OWN test iPad executable onto my MAC also. Just copied my iPad project to my MAC and rebuilt it. I did read you can run an iPad version on the latest MAC. Anyway I am targeting iPad, iPhone and MAC. HTH John

[quote='885415022, DTS Engineer, /thread/758325?answerId=885415022#885415022'] Looking at that it seems that the 26.5 betas should show improvements, but probably won’t fix all the cases of this. [/quote] Thanks for the update @DTS Engineer Quinn! What you’re reporting seems similar to my personal observations: with iOS 26.5 things might have gotten slightly better, but there are still some issues going on definitely. Have a great rest of the week!

@Steve4442 Quick FYI: I actually have the 2 different icons working now (Liquid Glass Icon Composer .icon appears in Tahoe, and my current Legacy .icns appears in Sequoia). It's a huge mess to do, but it is possible. In my case I had to: Generate a Legacy .icns via Terminal (instead of using an Asset Catalog in Xcode) Install Xcode 26.0.1 Create a simple test app with a Shell Script that runs actool to build the Asset.car file. Build my test app with Xcode 26.0.1 Copy the resulting Assets.car and the Terminal-built .icns, into my Xcode 24.3 production project. Tweak my Xcode 24.3 production project's Info.plist and build. Final app displays two different icons: LG in Tahoe, Legacy in Sequoia. To give you an idea of how messy this is, I had to follow much of John Siracusa's advice from here: https://mjtsai.com/blog/2025/08/08/separate-icons-for-macos-tahoe-vs-earlier/ If anyone really wants to go through this major hassle, I can try to write up instructions here. But it'll take me a while to write up

The update appeared after approximately 20 days. In-app events require at least five first-time downloads from unique Apple IDs before analytics results are displayed. When I reviewed the analytics, the event showed seven first-time downloads, which explains why the data became visible at that point. Based on this behavior, each in-app event needs a minimum of five first-time downloads for results to appear in analytics.

My colleagues are also facing the exact same issue. It looks like the browser after they click Accept Invitation takes them to https://appstoreconnect.apple.com/activation_ds?key=.... This page is just white with a spinning load icon. The browser network log shows that a GET call to https://appstoreconnect.apple.com/olympus/v1/termsOfService fails with a 401 error. See attached screenshot.

So the lead bug for this seems to be FB18764644. Looking at that it seems that the 26.5 betas should show improvements, but probably won’t fix all the cases of this. I don’t have any info to share as to whether a full fix will catch the macOS 26.5 bus or not. As always, I recommend that you re-test on beta releases as we seed them, although I recognise that testing for this particular bug is tricky, and gets trickier as we approach a complete fix. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='885154022, PolarBear3395, /thread/812992?answerId=885154022#885154022, /profile/PolarBear3395'] Is the only way to fix this literally to wipe your Mac and do a clean install? [/quote] It might be the only supported way to recover, but there are alternative approaches you might take. As your aware, the file system protections here are contingent on SIP being enabled, so you could: Disable SIP, make the change, re-enable SIP. Or boot into macOS Recovery and make the change from there. This isn’t supported because we don’t support changing data structures behind the back of running systems. Did anyone file a bug about this? Because I scanned this thread and can’t actually see a bug number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='885388022, pkahohi, /thread/823479?answerId=885388022#885388022, /profile/pkahohi'] Is there any mechanism to obtain a hashed or tokenized representation of the SIM/subscriber identity … ? [/quote] No. You could file an enhancement request for that, but I don’t fancy its chances. Such an API could be used for fingerprinting, which is something that Apple is actively working against. See the footnote about entropy at the bottom of this reply. [quote='885388022, pkahohi, /thread/823479?answerId=885388022#885388022, /profile/pkahohi'] are there any Apple-recommended approaches to uniquely distinguish between different SIM cards over time … ? [/quote] No, but an ER along those lines seems more viable to me. [quote='885388022, pkahohi, /thread/823479?answerId=885388022#885388022, /profile/pkahohi'] The gap is this [/quote] One way to close that gap would be for you to stand up a web service that allows your app to request some sort of authorisation token when that service is accessed over WWAN. Your app co

Thanks for all the details. Yeah, I’ve never been happy with the whole ‘running your app as command-line tool’ process. It seems very brittle, especially in situations like yours where the installer package, and hence the post-install script, runs outside of a user context. However, it is a documented, and hence supported, approach. Given that, we need to keep it working, so a bug report is called for. Before I send you off in that direction, however, I want to ask about this: [quote='885329022, pnelson, /thread/823493?answerId=885329022#885329022, /profile/pnelson'] My OS is 26.5 [/quote] Because macOS 26.5 is still in beta, it’d be to your advantage to determine whether this problem was introduced by that update. If you retest this on macOS 26.4, does it have the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com