Search results for

“DTiPhoneSimulatorErrorDomain Code 2”

162,370 results found

Post

Replies

Boosts

Views

Activity

App stuck in "Waiting for Review" for over 2 months
Hello everyone, I would like to ask whether other developers are currently experiencing unusually long App Review delays for new apps. Here is the timeline for my app (Apple ID: 6759361892): Build 1 — Feb 19, 2026: Initial build submitted Feb 21, 2026: Rejected because ads were not working properly Build 2 — Feb 23, 2026: Updated build submitted Build 3 — Feb 26, 2026: Another updated build submitted Mar 11–18, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 18, 2026: Submission cancelled and resubmitted Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent several follow-up emails regarding the delay Contacted Apple Support and asked them to leave messages for the App Review team Each time, I was told that the situation would be checked or that the review would “begin shortly.” I have now received that same
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
3
0
196
1w
Reply to CKQuerySubscription on public database failing with BAD_REQUEST in Production — distinct from iOS 26.4 silent-push regression
I don't have an immediate answer just yet, but would like to check the following: Are you testing with a device that is logged in with an iCloud account? Without a valid iCloud account, your app can't write to the CloudKit database. Do you have any special configuration on the security roles (CloudKit Console > Schema > Security Roles), which prevents the your account to write to the database? For debugging purpose, would you mind to try with visible notifications, as shown in the following code example? extension CKDatabase { public func addQuerySubscription(_ recordType: String, subscriptionID: String, predicate: NSPredicate? = nil, options: CKQuerySubscription.Options, operationQueue: OperationQueue? = nil, completionHandler: @escaping (CKSubscription?, Error?) -> Void) { let predicate = predicate ?? NSPredicate(value: true) let subscription = CKQuerySubscription(recordType: recordType, predicate: predicate, subscriptionID: subscriptionID, options: options) let notificationInfo = CKSubscr
Topic: App & System Services SubTopic: iCloud Tags:
1w
audiomxd PVM misclassifies CarPlay head unit as BTHeadphones — CarPlay never activates despite successful iAP2 auth
iPhone 16 Pro, iOS 26.5 (23F77), Nissan Sentra 2022, USB-C wired CarPlay. CarPlay fails every attempt despite the iAP2 handshake completing successfully. Same cable + same car works with a different iPhone. After digging through sysdiagnose logs I found the root cause in audiomxd. The head unit's Bluetooth MAC (BC:42:8C:B8:06:AF) is permanently stored in the PVM as HeadphonesBT: PVM: Route [58] = HeadphonesBT~BC:42:8C:B8:06:AF This causes FigRoutingManagerProcessCustomizedRouting to return: isPortOfTypeCarPlayAtIndex = NO modelID = BTHeadphones4236,19521 And vaemProcessCarPlayCustomizedRouting never adds a starkPort: portsToAdd[0] = AirPlayHandoffDevice portsToAdd does NOT contain a starkPort Without a starkPort the audio routing never activates. The endpoint gets published under endpointManager=Bluetooth as BluetoothHFPInput/Output instead of CarPlay. Disconnect follows with errors -16723 and -16617. This survives Forget Device, Forget Car, Reset Network Settings, and reboots. The only thing that clears it i
Topic: Media Technologies SubTopic: Audio Tags:
0
0
249
1w
Reply to M5 Pro DCP bandwidth allocation: asymmetric 27,400/13,700 Mbps split between dispext0/dispext1 on dual 5K configuration
Is the 27,400/13,700 Mbps asymmetric allocation observed on dual 5K configurations the expected manifestation of the two-pipe architecture described in thread 814201, or a distinct allocation policy specific to dual-display scenarios? Yes, it's the same general issue, though my pipe description there was more of a general analogy, not an engineering-level description. Note that you're driving the first monitor at 144Hz: 5120x2880 @ 144Hz, Maximum Source Bandwidth: 27,400 Mbps, HDR enabled ...which is more than the 120Hz required to drive both monitors at 5K. Is there a configuration approach that allows both displays to receive adequate bandwidth allocation? I believe this would work if a hardware adaptor restricted the first monitor to 120Hz. The WindowServer assertion failure in max_src_rect_width_by_pipes() This is a known issue (r.170248892), but it seems to be tied to monitor hot plug, particularly while the machine is asleep, not display allocation. __ Kevin Elliott DTS Engineer, CoreOS/Hardwar
Topic: App & System Services SubTopic: Hardware
1w
Reply to ExcUserFault and corrupted data when using UIImage#heicData
For the corruption you're seeing, UIImage(data:) returning nil is a fine detector. Tested against your corrupt HEIC alongside CGImageSourceCreateImageAtIndex, both return failure on the same data — UIKit's image construction goes through Image I/O internally, so the two checks likely overlap in what they catch. Either works for guarding the database write. Minor: what I suggested earlier was Image I/O (CGImageSource…), not Core Image. Different framework — worth knowing if you go looking at docs. Thanks for checking the threading. @MainActor on those call sites rules out simple concurrency around the calls. It doesn't rule out lower-level object-lifetime issues (the source image's backing data being released between heicData() and when the underlying encoder finishes), but those are unlikely to happen accidentally with the modern Photos and UIImage APIs. On the reproduction difficulty: since the guard catches the failure mode in your database, shipping it protects your customers even without a reprod
Topic: UI Frameworks SubTopic: UIKit Tags:
1w
App Store Connect 409 ENTITY_ERROR.RELATIONSHIP.INVALID — Cannot attach build to version record
This is my first time submitting an app for review. I'm unable to submit my iOS app for review due to a persistent 409 error when trying to attach a build to my App Store version record. This has been happening across multiple builds and version strings. { errors: [{ id: 80550434-590c-48c6-b2d3-5bd3b038539b, status: 409, code: ENTITY_ERROR.RELATIONSHIP.INVALID, title: The provided entity includes a relationship with an invalid value, detail: The specified pre-release build could not be added., source: { pointer: /data/relationships/build } }] } What I've tried: • Submitted build 34 (version 1.0) — same 409 error • Incremented to build 35, version 1.0.1 — same 409 error • Removed the build from the version page and re-added it — same error Environment: • Xcode 16 • iOS deployment target: 17.0 • Builds processed successfully in TestFlight (status: Ready to Submit) • Version record ID: 198605a5-2671-44d6-bacb-04157088319d Question: Has anyone encountered this? Is the version record itself corrupted/stuc
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
2
0
131
1w
Reply to iOS 26.5 SIGKILLs audio-recording app at ~50s of background despite UIBackgroundModes: audio - what is the supported API path?
So, this is the most critical detail to focus on: When the user starts a recording and locks the phone, iOS terminates our process with SIGKILL at approximately 50 seconds of continuous background time. I'm not sure why the system terminated your app, but I am confident that the crash log provides at least some guidance on the cause and that the system console provides a more in-depth description of the cause. That means your next steps here are: Looking at the crash log the system generated, particularly the top-level header that includes the exception code and reason. You can post the full crash log here as well, but the top-level header is what's most useful. If you look at the system log at the time your app is terminated, you can see the process that kills your app play out across our daemons. The termination itself was probably done by runningboardd and would have included some context data about what/who/why the termination occurred. You can also trace backward from that point in time, as what
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
1w
M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible
M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible Background This is a follow up to my November 2024 thread Keychain issues after installing backup on new Mac which was closed because I had a temporary workaround. That workaround using my wife's MacBook Air for signing is not sustainable. I used AI assistance to determine the root cause. My DTS case 102877839447 is open but has not yet been forwarded to a DTS engineer. Environment Mac Mini M4, macOS 15.4.1 (Build 25E253) Xcode 26.4.1 (17E202) Team ID: Q23726668V (Computerade Products) Working comparison machine: MacBook Air, macOS 15.3 Precise Bug — Reproducible Every Time Every time Xcode generates a new certificate and key pair on my Mac Mini: Certificate: Apple Development: Michael Birch (9KD5TCGGHG) ✅ Private key: Apple Development: Michael Birch (Computerade Products) ❌ The key uses the organization name instead of the certificate identifier. They never pair as a valid codesigning identity. security find-identity -v -p c
Topic: Developer Tools & Services SubTopic: Xcode
2
0
91
1w
Reply to WKWebView iOS 26 preventing javascript injections
This is unrelated to WKWebView and to the JavaScript-injection issue we were discussing. The app isn't reaching any code that uses WKWebView. yes i know but when its occured wanted to share with you For a launch crash like this, the fastest progress is usually a report to the .NET MAUI / Xamarin issue tracker, what is your suggestion? should i I clean install Rider macOS 26.1.2 (latest and simulator problem solved version) and Xcode & emulators? Run your Xcode 26 / iOS 26 SDK build on the iPhone 13 connected via USB. In Safari on the Mac, choose Develop → [Your iPhone] → [the entry for the WKWebView inside your app]. The entry will be labeled with your app's name or with the URL the WKWebView is currently showing — not Safari, which is a separate process. With the JavaScript console open, trigger the operation in your app that's failing. The errors (or silence) on the console will tell us which of the four scenarios from my previous message you're in. The test you described in NOTE-1 was the page
Topic: Safari & Web SubTopic: General
1w
Reply to NSInvalidArgumentException while sharing in UIDocumentInteractionController
Thanks for sending the three samples and the code snippet. They confirm the symptom (NSInvalidArgumentException: object cannot be nil from [__NSArrayM insertObject:atIndex:]) but don't yet narrow the source. I traced the symbol from your stack into the ShareSheet binary. The crash lands inside the block that processes activity items in loadItemProvidersForRequest:activity:completion:, in the branch that handles NSURL items. That branch resolves metadata for the file URL via LaunchServices and FileProvider, builds a security context, and constructs an NSArray from the result. The NSArray construction has no nil guard, so any nil reaching it throws the exception you see. On an iPhone 16 running iOS 26.4, I built a small reproducer that presents a downloaded PDF four ways: UIDocumentInteractionController.presentPreview, QLPreviewController, UIActivityViewController with the file URL, and UIActivityViewController with an NSItemProvider built from the PDF's bytes. None crashed. The three file-URL paths pr
Topic: UI Frameworks SubTopic: UIKit Tags:
1w
Reply to Repeatedly rejected for Guideline 2.5.4 despite clear UI, in-app onboarding, video, and detailed notes
Hi Suyog, I went through the exact same issue with AddFive, a fitness app using AVSpeechSynthesizer for voice coaching over AVAudioSession (.playback). Two 2.5.4 rejections with the same boilerplate before it went through. What I believe made the difference: a screen recording attached to the Resolution Center reply showing audio actively playing during a workout session, so the reviewer could see and hear the feature in context without having to find it themselves. Good luck, you're clearly doing everything right.
Topic: App Store Distribution & Marketing SubTopic: App Review
1w
Reply to receivedTurnEventForMatch giving stale data
Intermittent bugs are still worth filing — a Feedback Report doesn't need to reliably reproduce. It needs to give engineering enough information to identify the failure when it happens and to correlate against the server-side logs. A few things that make this kind of report useful: A sample project that uses the same receivedTurnEventForMatch → loadMatch(withID:) path. If you can extract that flow out of your game into a small standalone app that two test accounts can play against each other, that's ideal. If extracting is impractical, your actual app build can work too — engineering may follow up with what would help most. Logging that captures, for each receivedTurnEventForMatch: the timestamp, the match ID, the local player ID, the reported current participant, and the matchData state at that moment. Then for each retry: the timestamp, what was returned, and whether it matched the previous state. The match IDs and approximate timestamps from past occurrences you've observed. Engineering can cross-
Topic: Graphics & Games SubTopic: GameKit
1w
Reply to WKWebView iOS 26 preventing javascript injections
Thanks for sending the crash report. The simulator launch crash is a different issue from the JavaScript-injection problem we were tracking, and the good news is it doesn't have to block the JS debugging — more on that at the end. The simulator crash is a code-signing failure at dynamic load The most informative parts of the crash report: Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page Crashing thread: dyld_sim, in mach_o::UnsafeHeader::forEachLoadCommand / forEachSegment The crash happens about 3 ms after launch — the dynamic linker is still loading binaries from the .app bundle and your code never runs. What this means: as dyld maps pages of a binary into memory, the kernel verifies each page against the binary's code signature. One page doesn't match, the kernel terminates the process, and the crash report points at the mapped-file region that failed. The address (0x1014c4000) with Invalid Page wording typically indicates a page-hash mismatch — e
Topic: Safari & Web SubTopic: General
1w
Reply to Ios filenaming and metadata changing
Thanks for the question. A few clarifications first: The naming convention you're describing (IMG_XXXX, files in a DCIM folder) comes from the DCF specification — Design rule for Camera File system, established by JEITA. Most digital cameras, including iOS devices, follow it for interoperability with computers and other devices. The system Camera app uses DCF naming, and that behavior isn't user-configurable. You can't change how the built-in Camera app names the files it creates. However, you can build your own camera app that uses any naming convention you like — including IMG_YYYYMMDD_HHMMSS for photos and VID_YYYYMMDD_HHMMSS for videos. The same public frameworks the Camera app uses are available to every developer. One thing to keep in mind: even after you give a captured file a custom filename, the Photos app displays photos by date in its main UI rather than by filename. Filenames are visible in the asset's info panel, not the main grid view. So a custom filename helps when you export or share files, o
Topic: Media Technologies SubTopic: Photos & Camera
1w
App stuck in "Waiting for Review" for over 2 months
Hello everyone, I would like to ask whether other developers are currently experiencing unusually long App Review delays for new apps. Here is the timeline for my app (Apple ID: 6759361892): Build 1 — Feb 19, 2026: Initial build submitted Feb 21, 2026: Rejected because ads were not working properly Build 2 — Feb 23, 2026: Updated build submitted Build 3 — Feb 26, 2026: Another updated build submitted Mar 11–18, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 18, 2026: Submission cancelled and resubmitted Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent several follow-up emails regarding the delay Contacted Apple Support and asked them to leave messages for the App Review team Each time, I was told that the situation would be checked or that the review would “begin shortly.” I have now received that same
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
3
Boosts
0
Views
196
Activity
1w
Reply to CKQuerySubscription on public database failing with BAD_REQUEST in Production — distinct from iOS 26.4 silent-push regression
I don't have an immediate answer just yet, but would like to check the following: Are you testing with a device that is logged in with an iCloud account? Without a valid iCloud account, your app can't write to the CloudKit database. Do you have any special configuration on the security roles (CloudKit Console > Schema > Security Roles), which prevents the your account to write to the database? For debugging purpose, would you mind to try with visible notifications, as shown in the following code example? extension CKDatabase { public func addQuerySubscription(_ recordType: String, subscriptionID: String, predicate: NSPredicate? = nil, options: CKQuerySubscription.Options, operationQueue: OperationQueue? = nil, completionHandler: @escaping (CKSubscription?, Error?) -> Void) { let predicate = predicate ?? NSPredicate(value: true) let subscription = CKQuerySubscription(recordType: recordType, predicate: predicate, subscriptionID: subscriptionID, options: options) let notificationInfo = CKSubscr
Topic: App & System Services SubTopic: iCloud Tags:
Replies
Boosts
Views
Activity
1w
audiomxd PVM misclassifies CarPlay head unit as BTHeadphones — CarPlay never activates despite successful iAP2 auth
iPhone 16 Pro, iOS 26.5 (23F77), Nissan Sentra 2022, USB-C wired CarPlay. CarPlay fails every attempt despite the iAP2 handshake completing successfully. Same cable + same car works with a different iPhone. After digging through sysdiagnose logs I found the root cause in audiomxd. The head unit's Bluetooth MAC (BC:42:8C:B8:06:AF) is permanently stored in the PVM as HeadphonesBT: PVM: Route [58] = HeadphonesBT~BC:42:8C:B8:06:AF This causes FigRoutingManagerProcessCustomizedRouting to return: isPortOfTypeCarPlayAtIndex = NO modelID = BTHeadphones4236,19521 And vaemProcessCarPlayCustomizedRouting never adds a starkPort: portsToAdd[0] = AirPlayHandoffDevice portsToAdd does NOT contain a starkPort Without a starkPort the audio routing never activates. The endpoint gets published under endpointManager=Bluetooth as BluetoothHFPInput/Output instead of CarPlay. Disconnect follows with errors -16723 and -16617. This survives Forget Device, Forget Car, Reset Network Settings, and reboots. The only thing that clears it i
Topic: Media Technologies SubTopic: Audio Tags:
Replies
0
Boosts
0
Views
249
Activity
1w
Reply to M5 Pro DCP bandwidth allocation: asymmetric 27,400/13,700 Mbps split between dispext0/dispext1 on dual 5K configuration
Is the 27,400/13,700 Mbps asymmetric allocation observed on dual 5K configurations the expected manifestation of the two-pipe architecture described in thread 814201, or a distinct allocation policy specific to dual-display scenarios? Yes, it's the same general issue, though my pipe description there was more of a general analogy, not an engineering-level description. Note that you're driving the first monitor at 144Hz: 5120x2880 @ 144Hz, Maximum Source Bandwidth: 27,400 Mbps, HDR enabled ...which is more than the 120Hz required to drive both monitors at 5K. Is there a configuration approach that allows both displays to receive adequate bandwidth allocation? I believe this would work if a hardware adaptor restricted the first monitor to 120Hz. The WindowServer assertion failure in max_src_rect_width_by_pipes() This is a known issue (r.170248892), but it seems to be tied to monitor hot plug, particularly while the machine is asleep, not display allocation. __ Kevin Elliott DTS Engineer, CoreOS/Hardwar
Topic: App & System Services SubTopic: Hardware
Replies
Boosts
Views
Activity
1w
Reply to ExcUserFault and corrupted data when using UIImage#heicData
For the corruption you're seeing, UIImage(data:) returning nil is a fine detector. Tested against your corrupt HEIC alongside CGImageSourceCreateImageAtIndex, both return failure on the same data — UIKit's image construction goes through Image I/O internally, so the two checks likely overlap in what they catch. Either works for guarding the database write. Minor: what I suggested earlier was Image I/O (CGImageSource…), not Core Image. Different framework — worth knowing if you go looking at docs. Thanks for checking the threading. @MainActor on those call sites rules out simple concurrency around the calls. It doesn't rule out lower-level object-lifetime issues (the source image's backing data being released between heicData() and when the underlying encoder finishes), but those are unlikely to happen accidentally with the modern Photos and UIImage APIs. On the reproduction difficulty: since the guard catches the failure mode in your database, shipping it protects your customers even without a reprod
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
1w
App Store Connect 409 ENTITY_ERROR.RELATIONSHIP.INVALID — Cannot attach build to version record
This is my first time submitting an app for review. I'm unable to submit my iOS app for review due to a persistent 409 error when trying to attach a build to my App Store version record. This has been happening across multiple builds and version strings. { errors: [{ id: 80550434-590c-48c6-b2d3-5bd3b038539b, status: 409, code: ENTITY_ERROR.RELATIONSHIP.INVALID, title: The provided entity includes a relationship with an invalid value, detail: The specified pre-release build could not be added., source: { pointer: /data/relationships/build } }] } What I've tried: • Submitted build 34 (version 1.0) — same 409 error • Incremented to build 35, version 1.0.1 — same 409 error • Removed the build from the version page and re-added it — same error Environment: • Xcode 16 • iOS deployment target: 17.0 • Builds processed successfully in TestFlight (status: Ready to Submit) • Version record ID: 198605a5-2671-44d6-bacb-04157088319d Question: Has anyone encountered this? Is the version record itself corrupted/stuc
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
2
Boosts
0
Views
131
Activity
1w
Reply to iOS 26.5 SIGKILLs audio-recording app at ~50s of background despite UIBackgroundModes: audio - what is the supported API path?
So, this is the most critical detail to focus on: When the user starts a recording and locks the phone, iOS terminates our process with SIGKILL at approximately 50 seconds of continuous background time. I'm not sure why the system terminated your app, but I am confident that the crash log provides at least some guidance on the cause and that the system console provides a more in-depth description of the cause. That means your next steps here are: Looking at the crash log the system generated, particularly the top-level header that includes the exception code and reason. You can post the full crash log here as well, but the top-level header is what's most useful. If you look at the system log at the time your app is terminated, you can see the process that kills your app play out across our daemons. The termination itself was probably done by runningboardd and would have included some context data about what/who/why the termination occurred. You can also trace backward from that point in time, as what
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Replies
Boosts
Views
Activity
1w
M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible
M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible Background This is a follow up to my November 2024 thread Keychain issues after installing backup on new Mac which was closed because I had a temporary workaround. That workaround using my wife's MacBook Air for signing is not sustainable. I used AI assistance to determine the root cause. My DTS case 102877839447 is open but has not yet been forwarded to a DTS engineer. Environment Mac Mini M4, macOS 15.4.1 (Build 25E253) Xcode 26.4.1 (17E202) Team ID: Q23726668V (Computerade Products) Working comparison machine: MacBook Air, macOS 15.3 Precise Bug — Reproducible Every Time Every time Xcode generates a new certificate and key pair on my Mac Mini: Certificate: Apple Development: Michael Birch (9KD5TCGGHG) ✅ Private key: Apple Development: Michael Birch (Computerade Products) ❌ The key uses the organization name instead of the certificate identifier. They never pair as a valid codesigning identity. security find-identity -v -p c
Topic: Developer Tools & Services SubTopic: Xcode
Replies
2
Boosts
0
Views
91
Activity
1w
Reply to WKWebView iOS 26 preventing javascript injections
This is unrelated to WKWebView and to the JavaScript-injection issue we were discussing. The app isn't reaching any code that uses WKWebView. yes i know but when its occured wanted to share with you For a launch crash like this, the fastest progress is usually a report to the .NET MAUI / Xamarin issue tracker, what is your suggestion? should i I clean install Rider macOS 26.1.2 (latest and simulator problem solved version) and Xcode & emulators? Run your Xcode 26 / iOS 26 SDK build on the iPhone 13 connected via USB. In Safari on the Mac, choose Develop → [Your iPhone] → [the entry for the WKWebView inside your app]. The entry will be labeled with your app's name or with the URL the WKWebView is currently showing — not Safari, which is a separate process. With the JavaScript console open, trigger the operation in your app that's failing. The errors (or silence) on the console will tell us which of the four scenarios from my previous message you're in. The test you described in NOTE-1 was the page
Topic: Safari & Web SubTopic: General
Replies
Boosts
Views
Activity
1w
Reply to NSInvalidArgumentException while sharing in UIDocumentInteractionController
Thanks for sending the three samples and the code snippet. They confirm the symptom (NSInvalidArgumentException: object cannot be nil from [__NSArrayM insertObject:atIndex:]) but don't yet narrow the source. I traced the symbol from your stack into the ShareSheet binary. The crash lands inside the block that processes activity items in loadItemProvidersForRequest:activity:completion:, in the branch that handles NSURL items. That branch resolves metadata for the file URL via LaunchServices and FileProvider, builds a security context, and constructs an NSArray from the result. The NSArray construction has no nil guard, so any nil reaching it throws the exception you see. On an iPhone 16 running iOS 26.4, I built a small reproducer that presents a downloaded PDF four ways: UIDocumentInteractionController.presentPreview, QLPreviewController, UIActivityViewController with the file URL, and UIActivityViewController with an NSItemProvider built from the PDF's bytes. None crashed. The three file-URL paths pr
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
1w
Reply to Repeatedly rejected for Guideline 2.5.4 despite clear UI, in-app onboarding, video, and detailed notes
Hi Suyog, I went through the exact same issue with AddFive, a fitness app using AVSpeechSynthesizer for voice coaching over AVAudioSession (.playback). Two 2.5.4 rejections with the same boilerplate before it went through. What I believe made the difference: a screen recording attached to the Resolution Center reply showing audio actively playing during a workout session, so the reviewer could see and hear the feature in context without having to find it themselves. Good luck, you're clearly doing everything right.
Topic: App Store Distribution & Marketing SubTopic: App Review
Replies
Boosts
Views
Activity
1w
Reply to receivedTurnEventForMatch giving stale data
Intermittent bugs are still worth filing — a Feedback Report doesn't need to reliably reproduce. It needs to give engineering enough information to identify the failure when it happens and to correlate against the server-side logs. A few things that make this kind of report useful: A sample project that uses the same receivedTurnEventForMatch → loadMatch(withID:) path. If you can extract that flow out of your game into a small standalone app that two test accounts can play against each other, that's ideal. If extracting is impractical, your actual app build can work too — engineering may follow up with what would help most. Logging that captures, for each receivedTurnEventForMatch: the timestamp, the match ID, the local player ID, the reported current participant, and the matchData state at that moment. Then for each retry: the timestamp, what was returned, and whether it matched the previous state. The match IDs and approximate timestamps from past occurrences you've observed. Engineering can cross-
Topic: Graphics & Games SubTopic: GameKit
Replies
Boosts
Views
Activity
1w
Reply to WKWebView iOS 26 preventing javascript injections
Thanks for sending the crash report. The simulator launch crash is a different issue from the JavaScript-injection problem we were tracking, and the good news is it doesn't have to block the JS debugging — more on that at the end. The simulator crash is a code-signing failure at dynamic load The most informative parts of the crash report: Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page Crashing thread: dyld_sim, in mach_o::UnsafeHeader::forEachLoadCommand / forEachSegment The crash happens about 3 ms after launch — the dynamic linker is still loading binaries from the .app bundle and your code never runs. What this means: as dyld maps pages of a binary into memory, the kernel verifies each page against the binary's code signature. One page doesn't match, the kernel terminates the process, and the crash report points at the mapped-file region that failed. The address (0x1014c4000) with Invalid Page wording typically indicates a page-hash mismatch — e
Topic: Safari & Web SubTopic: General
Replies
Boosts
Views
Activity
1w
Reply to WeatherKit: WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 on iOS 26.2 (Simulator & Device)
I am getting that error as well with one app that I am developing, while another app that I made works fine with, as far as I know, the same settings etc., and very similar code.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Ios filenaming and metadata changing
Thanks for the question. A few clarifications first: The naming convention you're describing (IMG_XXXX, files in a DCIM folder) comes from the DCF specification — Design rule for Camera File system, established by JEITA. Most digital cameras, including iOS devices, follow it for interoperability with computers and other devices. The system Camera app uses DCF naming, and that behavior isn't user-configurable. You can't change how the built-in Camera app names the files it creates. However, you can build your own camera app that uses any naming convention you like — including IMG_YYYYMMDD_HHMMSS for photos and VID_YYYYMMDD_HHMMSS for videos. The same public frameworks the Camera app uses are available to every developer. One thing to keep in mind: even after you give a captured file a custom filename, the Photos app displays photos by date in its main UI rather than by filename. Filenames are visible in the asset's info panel, not the main grid view. So a custom filename helps when you export or share files, o
Topic: Media Technologies SubTopic: Photos & Camera
Replies
Boosts
Views
Activity
1w