https://github.com/docker/for-mac/issues/7527 suggests a way to fix it. macOS 15.4.1 has also been released, but I doubt that will make any difference, as "the reason for this warning is that some files in existing installations are incorrectly signed."

This is how it's supposed to work, isn't it? A user in Ukraine will be viewing the Ukraine App Store, which shows prices in UAH. Why would Ukrainian App Store users want to see prices in USD? They'd have to convert it to UAH in their heads. There are settings in App Store Connect for your products that deal with the pricing. I'm not sure how much you can tweak it, but you might want to have a look in there and see if there's something you want to change. If I've misunderstood your question, please feel free to provide more clarity.

Doesn't the completion handler have to be called within the method? (as in, does Code force you to return something from the method?) If not, it should be fine because it just doesn't mark that you've got new data; it didn't complete. If your widget doesn't receive any updates, it should be written to handle missing data. As an example, add the Apple Weather widget to your Home Screen. Turn off your Wi-Fi, mobile data etc. and see what it looks like. It says it can get data right now. Your widget should handle no data in a similar way.

Attach the image to THIS thread. I'm not clicking a random unknown url that you've shortened.

Speak to Elgato. No one here can bring this app to the Apple TV for you. I want my brother to wash my car. Why am I telling you? These are the Developer Forums, where third-party, not-employed-by-Apple-or-Elgato developers of apps for Apple's platforms ask each other for hints and tips on coding their own apps. You're in the wrong place.

Right. Have you raised a bug, or are you hoping someone at Apple will come across your post in these Developer Forums (which are for random third-party not-employed-by-Apple developers) and raise the bug for you? Please raise a Feedback report at https://feedbackassistant.apple.com/ then post the FB number here.

Chill. Where are you in the process? Is there a screenshot you can share that shows what you're talking about? (Redact any personal information if it's on the screen.)

Slot? Where? In App Store Connect? Xcode? Got a screenshot so we can see what you're talking about?

I think you need to report the crash to Zoom, not to us third-party not-employed-by-Apple random developers on these forums.

Put the call to modelContext.fetch() inside a try { ... } catch { ... } block, and print out the error that it catches. If you're trying to do something but you aren't bothering to catch any errors to see why it's failing, you're going to hit issues like this. Your current code is always assuming that everything is 100% tickety-boo all the time. If transactions was nil, the call to transaction.count would crash the app anyway.

An EXC_BAD_ACCESS is happening because you're trying to access a resource that no longer exists, so it looks like something in your code is trying to do 'something' with that window after you've told it to be released when it's closed. You need to debug your code and ensure you're not trying to do anything with released resources.

What platform versions are you running this on? What version of iOS? What version of macOS? What version of Xcode? And, how wide is the window that you took the Second View screenshot of? Does the back arrow (or the title) appear in the right location if the window is wider? What happens if you resize the macOS window while it's running? Do the arrow and title draw correctly?

Wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. This isn't the place to advertise your wares.

What conversation? Could you maybe just give us an example of what you're talking about? Give us some code and explain what the issue is and what the current workaround is. If you believe it's a bug, why not just raise it? https://feedbackassistant.apple.com/ then post the FB number here.

Not sure if this is the problem, but you're passing by reference that error variable into that call, but you've set it to nil, so if there's an error in that call it can't write that error to that variable because it's nil. Try: NSError *error; instead. Then, when inspecting the results of that call, you need to check if error is nil before trying to access its contents.