“smb big sur”

My question is: Is this pattern—creating a new, temporary ModelContext inside each of these entities(for:) functions (and presumably inside all the other required query/data-import functions for all of my entity types)—the correct way to bridge the gap between the UUID requirement from AppEntity and my PersistentIdentifier-based actor? Yes. ModelContext.init(_ container: ModelContainer) returns a nonisolated context. In case you don't use the context and its associated model instances outside of the current actor, you will be fine. My question is: Is there a recommended way to convert a PersistentIdentifier into a String (to pass to the intent) and then reliably convert that String back into a PersistentIdentifier inside the intent's perform() method? There isn't. In Core Data, NSManagedObjectID provides uriRepresentation(), which returns a URL that can be converted to a string and vice versa. PersistentIdentifier instead exposes an id (ID), which is opaque. The alternative seems to be passing the UUID string

Ed addressed your specific question, but I want to address about the big picture… It seems like your goal is to downgrade an iOS device from a newer version of iOS to an older version. There’s no supported way to do that [1] on iOS or any of its ‘child’ platforms [2]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] The only exception being during the beta cycle of a new OS, where it’s possible to erase and device and install the most recent non-beta OS. [2] It is possible to do this with macOS.

I sympathise with you. 🥲 SwiftUI may be great in some aspects, but I often find that fine tuning to achieve a precise UI behaviour is a nightmare. When it is impossible to understand why SwiftUI reacts in a certain way, you end up spending enormous time just to turn around SwiftUI to mimic UIKit behaviour. Big sigh.

I too have this issue. It prevents audio recording on both the iOS screen recording as well as 3rd party apps like AnyMiro and Reflector 4. This is a big problem for me as I try to make demo videos of my app.

There are three different questions here, so let me tackle them in turn. [quote='805211021, nikhil2701, /thread/805211, /profile/nikhil2701'] Are the Wifi-Aware's WAEndpoint’s discovered ephemeral? [/quote] That’s a matter of definition (-: Our recommendation is that you treat an endpoint like other networking objects, that is, it’s fine to continue using it while your app is running, but it’s best to drop it when your app gets suspended [1]. Also, keep in mind that you can only connect while the publisher is still running, and that gets increasingly unlikely as time goes by. [quote='805211021, nikhil2701, /thread/805211, /profile/nikhil2701'] What is the impact on the infrastructure wifi here in comparison to using the Apple peer to peer wifi … ? [/quote] Wi-Fi Aware certainly can have an impact on infrastructure Wi-Fi. I don’t have any concrete info about that impact, or how it compares to Apple peer-to-peer Wi-Fi. However, you will likely see a difference depending on how you use Wi-Fi Aware, and specifica

I’m not sure what happened here. Generally, when there’s a new agreement pending, the Developer website makes it very obvious as soon as you enter Developer > Account. There’s a big banner at the top and the act of agreeing to the update is quite explicit. Unfortunately this stuff is hard to test because you can’t undo your agreement. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

“Submitting a Rejection Appeal” I have already submitted this, but I doubt the team will fully understand the situation and that my account will be reopened, because I am currently being unfairly labeled with a “Pending Termination Notice” and “Evidence of Dishonest or Fraudulent Activity.” Please look at the screenshots. I am already trying to contact the App Store Connect team, but they suspend my account without even giving a warning. There is a big problem here, the account cannot be suspended that easily. There are people who abuse their position.

Started happening on Xcode 26.0.1 or were you successful with that version of Xcode? To clarify, it works properly with an iOS app upload. It is only for MacCatalyst app. So Xcode 26.0.1 works for ios and not for MacCatalyst. Have you tried today to submit one to TestFlight? I have, twice, still been getting the same issue. I will try again later today. Do you have all the logs? I have the build logs. But it is too big to attach to this reply. I will add it to the bug report.

What I don't understand from the reviewer's response is what receipts validation are they talking about? When a user makes a purchase, it creates a receipt in the app bundle. Your app should check the validity of that receipt. If it is valid, then you make the premium features available. If you don't validate the receipt, then hackers will re-distribute your app with a fake receipt so that anyone can use it for free. They might even charge a fee, making money off your app instead of you. Don't assume you're too small to be targeted. I assure you that you're not. I have no payment servers (the whole concept of using Apple's in-app-purchases service is to not have to deal with my own payment implementation) That's something totally different. Most apps are subscription based or have some service provided over the internet. For these use cases, Apple provides a quick-and-easy way to validate receipts. In your case, since you're entirely on-device, you'll need to validate the receipt on-device. That's tricky beca

I tried .otherNavigation and .other Also, it is not snapping to roads, at all. It is just that when the ship moves slowly, it does not really update the reported position, insteads it stays around the current position for a while and later makes a big jump to a new area where it resides then. The behaviour seems to occur less often if the ship is travelling faster (e.g. downstream). I parsed the internal locationd logs for GNSS NMEA messages and resolved positions and related them. The NMEA reported raw positions are plotted in blue, the resolved positions are plotted as green circles with their radius being the reported accuracy, and there are faint orange arrows pointing from NMEA positions to the afterwards resolved positions which are then reported to the apps.

This sounds related to my feedbacks FB16246168 (Text in Lock screen accessory rectangular widget does not wrap to another line when it should fit) FB16246023 (Lock screen accessory rectangular widget does not appear as expected on iPhone 16 Pro because text is too big and truncated) But both of those were filed before iOS 26

I’m not going to be able to help you with this. We don’t support folks killing arbitrary system processes. This is problematic for a variety of reasons, but the big issue here is that the name, location, and behaviour of system processes are all implementation details. If you build a product that relies on such implementation details, you are likely to run into compatibility problems down the line. Which is exactly what’s happened in this case )-: My advice is that you find an alternative way to achieve your ultimate goal. If you’re unable to do so, I recommend that you file an enhancement request for a supported path forward, making sure to explain your requirements and the reasons why the current mechanism don’t work for you. If you do file an ER, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com