“show when run”

[quote='823524021, Youssef-Hammad, /thread/823524, /profile/Youssef-Hammad'] how do crash reporters work on macOS ? [/quote] They don’t )-: Well, not in all circumstances |-: I have a long and involved explanation of crash reporting techniques in Implementing Your Own Crash Reporter. On macOS you have more flexibility than you do on iOS, in that you can do crash reporting both in and out of process. Sadly, neither is a good option: With in-process crash reporting your crash reporter can fail due to the process’s state being corrupted, which is the sort of thing that triggered a crash in the first place. When working out-of-process it’s hard for the crash report to get access to the information it needs in a supported way, that is, something that’ll work in the long term. Regarding your specific issue: [quote='823524021, Youssef-Hammad, /thread/823524, /profile/Youssef-Hammad'] [can I] avoid the normal macOS dialog entirely [/quote] Not in any supported fashion. The issue here is that the exact hook used by th

How is your installer invoking SMAppService? By running the app as a command-line tool from the post-install script? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I had another think about this. How about using .position(x:, y:) to move the image? Just tried this code, and it looks good for AccessoryCircular, AccessoryInline, AccessoryRectangular, Smart Stack Circular and Smart Stack Rectangular, but is slightly off for AccessoryCorner, so again, you'll have to fiddle with the numbers for at least one of the types: GeometryReader { g in ZStack { // I added this circle to show where it is in the view Circle() .foregroundColor(Color.blue) Image(systemName: circle.dashed) .resizable() .scaledToFit() .foregroundColor(.green) .position(x: g.size.width / 2 + 0.5, y: g.size.height / 2 + 0.5) // The 0.5 is the part that moves it to the right and down a little Text(9/9) .foregroundStyle(.primary) .font(.caption) .fontWeight(.semibold) } .widgetAccentable() }

@Quappi I'm the confused one. Provide a focused project showing what you trying to accomplish and that the API is doing currently. However you FB numbers you are in contact with the correct team, I would wait for their answer about your questions on that bug report. Albert
  Worldwide Developer Relations.

@BigBalli Thanks, BigBalli. It's not about the product identifier because an old Mac App Store application that has been available also fails in the same manner. Also, it's not about the configuration, because, I created a new one, but an old Mac App Store application still manages to fail in the same manner. The current situation is a total mess. I guess I should not have installed Xcode 26. Now, I cannot even sign in and out of an iCloud account so easily. The System keeps running a progress wheel for an hour. I'm bending towards buying a new Mac mini. I'm waiting for a new model with M5.

I'm happy to file a bug if desired and use whatever utilities would help to gather info for that. If you want this to change, filing bugs is the best approach. Keep in mind that this isn't really about the investigation side (the problem itself is well understood), it's about documenting the problems this is creating and that you want us to fix it. Once it's filed, please post the bug number back here so I can make sure it gets to the right place. I just wanted to add my voice to this thread to show that it's more widespread. I'm happy to explain what I can, but bugs are what get problems fixed. I know the Max's have (and I might be saying this wrong) more dedicated graphics cores and maybe that results in dedicated pipelines per monitor which is why it doesn't get confused? Yes, that's basically correct. I know it's not the OS or the kernel (right?) No, it's a kernel/OS issue. The kernel driver needs to be able to reconfigure itself and there needs to be infrastructure in user space to tell the kern

Starting somewhere around macOS 26.3, my sandboxed file manager spontaneously loses access to ~/Library/Mobile Documents mid-session. Just to clarify, by file manager do you mean that your app is doing its own navigation of the broader file system or that your app is a file provider extension? If you're a file provider extension, why do you need/want access to so much of the system? What makes this specific to FP-backed paths: regular paths under the same '/' bookmark (~/Library/Application Support, etc.) stay accessible and recover normally with a fresh start AccessingSecurityScopedResource() call. Only ~/Library/Mobile Documents and its subtree fail - the entire tree, including the parent directory itself. What other directories have you tried? Particularly directories user directories like ~/Documents/ or ~/Downloads/? Looking at the bug, the current theory is that this is actually tied to a difference between the sandbox extension originally issued by the open panel and the new extension issued when the b

Seen this one a lot. Subscription is unavailable in the current storefront almost always comes down to one of these, in order of likelihood: Paid Apps Agreement isn't in Active state for the team. Open App Store Connect > Agreements, Tax, and Banking. If the Paid Apps agreement shows anything other than Active (Action Required, missing bank info, missing tax forms, or a contact who's no longer on the team), every subscription rejects with this exact error until it's resolved. The subscription's price schedule doesn't include the user's storefront. Each subscription has pricing set per country. If you only configured prices for some countries, users outside that list get this error. Check the Price tab on the subscription and confirm the user's country is covered. The app and the subscription are in different availability regions. Even with pricing set, the app itself must also be available in that country. Check App Availability on the main app page. The subscription isn't actually in Ready for Sa