“show when run”

Same issue i'm experiencing. I paid on the 14th of April, i received the receipt immediately and can see the subsription active but on web it's still showing pending. I've logged 2 tickets but no response since last week Would really love to get this sorted out asap

[quote='885202022, boilerla220, /thread/820379?answerId=885202022#885202022, /profile/boilerla220'] I guess worth clarifying also is what is meant by user session. [/quote] Right. I generally try to follow the terminology from TN2083 Daemons and Agents. A system extension [1] is effectively a launchd daemon and thus runs in the global context. It can’t reliably access the window server. And any XPC service it calls upon will be similarly restricted. However, the GPU lifecycle isn’t tied directly to the window server lifecycle, so there is some wiggle room there, and that’s the point I’m still working to clarify internally. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Non-DEXT system extensions. DEXTs are weird (-:

I’m not going to be able to answer questions about FIPS compliance, which is more of a legal issue than a technical issue. You might have more luck asking this over in the Apple Support Community, run by Apple Support, and specifically in the Business and Education topic area. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[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