“DTiPhoneSimulatorErrorDomain Code 2”

The MagSafe 3 cable is an amazing piece of engineering, showing charged as green and charging as amber. Please consider that carging, and full or reached charging limit, is green, but in case you are far away, you need an estimate of battery percentage. A software magsafe update, like macOS 26.5 was very noticeable for me, as i have the charging limit set on 80%. A new MagSafe 4 would be a simple MagSafe 3 update, adding a yellow colour. it should be simple, here is the code: // 1. CRITICAL SAFETY CUT-OFF // If the system detects a hardware/thermal failure, // it cuts power and pulses RED. if (criticalError) { setLED(PULSING_RED); return; } // 2. SLOW CHARGER DETECTION // Logic: Air < 30W OR Pro < 70W triggers Pulsing Yellow. if ((isAir() && wattage < 30) || (isPro() && wattage < 70)) { setLED(PULSING_YELLOW); return; } // 3. CAPACITY GRADIENT // Simple, clear visual feedback based on your percentages. if (soc < 50) { setLED(COLOR_AMBER); // 0-50% } else if (so

When I submit an https web request I receive both of those funny errors. In particular I do not understand what that “Sectigo Public Server Authentication” message represents, perhaps yet another certification for Apple to access the request, when of course by connecting to that web address on Safari produces no errors. Connection error: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} (+[PPSClientDonation isRegisteredSubsystem:category:]) Permission denied: Maps / SpringfieldUsage (+[PPSClientDonation sendEventWithIdentifier:payload:]) Invalid inputs: payload={ isSPR = 1; } urlstring=https://taxiprofessional.net/***.php process loading

Good Day All, I am new to the forum so not sure if I am posting this in the correct category. I have 2 other apps that are running successfully on appstore so I am not fresh when it comes to creating apps. :) but I have hit a wall with the one I am currently busy with and need some help to figure out the next step please. Currently I have a app that is fully built and working perfect in testflight. However, the app connects to specifically Garmin watches to get specific triggers. When you pair the app with your watch it looks for the GarminConnect app on your phone for the details and then links it. I have the companion Garmin app for the watch on the Garmin store and that is approved. All good that also works. But when I send the app for review so I can release it I get the following response from the team : Guideline 5.2.1 - Legal - Intellectual Property Issue Description The app includes content or features from Garmin, or is marketed to control external hardware from Garmin, without the necessary

I'm trying to update the iCloud data handling in our app, and I'm running into an issue with a particular file on one particular device. This file never downloads & I haven't been able to pinpoint what's off about it. Right now we just have 2 iCloud accounts & a handful of devices, so I haven't been able to narrow it down yet, but in most cases, all the cloud files download as expected. However, whether or not the file eventually downloads, the NSURLUbiquitousItemDownloadRequestedKey key seems to be completely useless. For the following code: NSError *error = nil; BOOL success = [[NSFileManager defaultManager] startDownloadingUbiquitousItemAtURL:self.fileURL error:&error]; if (!success) { NSLog(@error downloading %@ : %@, self.fileURL, error); } else { NSDictionary *resourceValues = [self.fileURL resourceValuesForKeys:@[NSURLUbiquitousItemDownloadRequestedKey, NSURLUbiquitousItemIsDownloadingKey, NSURLUbiquitousItemDownloadingErrorKey, NSURLUbiquitousItemDownloadingStatusKey] err

I would like to ask for clarification regarding the specifications of Apple Subscriptions. We are currently planning a subscription discount campaign using Offer Codes, and during testing we encountered the following issue. Test scenario: A user who does not have our app installed accesses a URL that contains an Offer Code. The App Store opens and displays the details of the Offer Code. The user reviews the offer and proceeds, at which point the App Store prompts the user to install our app. The user installs the app and launches it. Issue: The subscription remains in an unpurchased state. From the app implementation side, when the app launches, we attempt to retrieve transactions held by Apple using unfinishedTransactions. However, no transaction is returned, so the app cannot transition the user to a subscribed state. In contrast, when a user who already has the app installed accesses the Offer Code URL (step 1), the app can successfully retrieve the unfinished transactio

(Note: I don't need DTS support. This is not a DTS issue, and the standard responses aren't relevant to the situation. I would ask that DTS not respond in lieu of the developer support official) Yesterday, a poster in this forum wrote about his experience waiting several months to get approved to have his apps notarized. He had hit the status code 7000; Team ID not configured for notarization block. An Apple Developer Support account responded to him saying they would help the poster. After a month of waiting and praying for Developer Support to approve my Team ID for notarization, and no progress via the official channels, I am rolling the dice that asking Developer Support here will get my account approved or at least moved forward. I just can't wrap my head around why it takes so long to allow a Team ID to submit apps for notarization. My Team ID is V67NRZ84A2, and my support ticket is 102874600970. Spending months and months developing an app, paying the Developer Support annual fee, and then hav

Hey team, This is a weird one, when Siri + On-Screen Actions are enabled in the Apple TV settings (General Settings), LazyVStack experiences severe main-thread hangs and very high CPU usage. The issue only occurs when Siri + On-Screen Actions are enabled in Apple TV device settings (General Settings). Disabling On-Screen Actions completely resolves the issue. The issue has been verified on multiple Apple TV devices, running tvOS 26.3, 26.4 and 26.5. The behavior was not observed in Simulators, only on an actual device. This seems to be caused by some type of accessibility overlap with SwiftUI. Running the below code with On-Screen Actions enabled in the Siri settings will demonstrate a complete hang of the CPU at 100% struct TestData { let id = UUID() var title: String } struct TestView: View { @State private var test: [TestData] = [] var body: some View { ScrollView { LazyVStack { ForEach(self.test, id: .id) { data in Button { } label: { Text(data.title) } } } } .task { var arr: [TestData] = [] for

Context We're handling App Store subscriptions on the server side using App Store Server Notification v2. Our pipeline currently identifies each event by transactionId and originalTransactionId. A few notes about our client: Our app is built with Flutter and uses the standard in_app_purchase plugin layer to drive App Store purchases (StoreKit 1 under the hood). We have not migrated to StoreKit 2 on the client yet. We have not been setting SKPayment.applicationUsername on outgoing purchases, so every transaction we've ever produced has appAccountToken: null in its v2 notification. This question is purely about what the server-side notification can tell us, given the current client state above. What we're trying to figure out A user can resubscribe to an expired subscription in two different places: In-app — the user opens our app and re-purchases through our normal in-app purchase flow. App Store — the user goes to Settings → Apple ID → Subscriptions and resubscribes from the system UI, witho