DTiPhoneSimulatorErrorDomain Code 2

I am developing an iOS application that utilizes running workout data from the iOS Health app / Fitness app via HealthKit, with explicit user permission. Before finalizing the app design, I would like to clarify several technical aspects related to data reliability, manual entry, record modification, and GPS route availability in HealthKit. My questions are as follows: 1. Identifying manually added (non-physical) running workouts When a running workout is created in the Health app without actual physical movement (for example, a workout manually added by the user), is there any metadata, flag, or key in HealthKit that allows developers to distinguish these records from workouts generated through actual motion tracking (iPhone or Apple Watch)? 2. Editing existing running workout records Is it possible for users, or for third-party apps with HealthKit write permission, to edit an existing running workout (e.g., distance, duration, calories) after it has been saved? • If edits are allowed, are the origi

I am encountering a persistent error in App Store Connect when attempting to save URLs in the App Clip URLs section of my app version. The issue is as follows: When I enter the URL (e.g., https://4o.c.smart321.com/c/l0) and click save, I receive a 409 Conflict error with the code ENTITY_ERROR.ATTRIBUTE.TYPE. The error detail states: does not match the uri pattern must be a valid RFC 3986 URI. The Error Log: { errors : [ { id : 9f032dd6-f456-4c90-ad9c-245c5ed041d7, status : 409, code : ENTITY_ERROR.ATTRIBUTE.TYPE, title : An attribute in the provided entity has the wrong type, detail : does not match the uri pattern must be a valid RFC 3986 URI, source : { pointer : /data/attributes/invocationUrls/1 } } ] } Conflicting Status: Interestingly, the exact same URL has already been configured under Advanced App Clip Experiences, where it currently shows a status of Received. My AASA file is https://4o.c.smart321.com/.well-known/apple-app-site-association I have verified that the URL follows the st

I have configured all the necessary settings for the APP Clip, but it still cannot be activated through NFC or scanning the code. What is the problem?

APP Stroe has created an advanced lightweight app experience, but NFC and QR code scanning are not activated. What is the problem?

I have the following code (compile as a standalone file): #import @interface AppDelegate : NSObject @property (strong) NSWindow *window; @end @implementation AppDelegate - (void)applicationDidFinishLaunching:(NSNotification *)notification { // Create main window self.window = [[NSWindow alloc] initWithContentRect:NSMakeRect(100, 100, 800, 600) styleMask:(NSWindowStyleMaskTitled | NSWindowStyleMaskClosable | NSWindowStyleMaskResizable | NSWindowStyleMaskMiniaturizable) backing:NSBackingStoreBuffered defer:NO]; [self.window setTitle:@Nested ScrollView Demo]; [self.window makeKeyAndOrderFront:nil]; // Split view controller NSSplitViewController *splitVC = [[NSSplitViewController alloc] init]; // Sidebar NSViewController *sidebarVC = [[NSViewController alloc] init]; sidebarVC.view = [[NSView alloc] initWithFrame:NSMakeRect(0, 0, 200, 600)]; sidebarVC.view.wantsLayer = YES; NSSplitViewItem *sidebarItem = [NSSplitViewItem sidebarWithViewController:sidebarVC]; sidebarItem.minimumThickness = 150; sidebarIt

When I try to invoke the tkinter module in Python 3 that is bundled with Xcode Developer Tools, I get a message saying that my system version is too low: $ /usr/bin/python3 -m tkinter macOS 26 (2602) or later required, have instead 16 (1602) ! zsh: abort /usr/bin/python3 -m tkinter It seems like the system version reported is macOS 16, which I assume is the version code before the decision to rename all OS platforms to 26. This is a very low level mistake and should be fixed as soon as possible.

Hello, Our iOS app (Flutter + Swift) was rejected under Guideline 2.5.1 with the following message: The app uses or references the following non-public or deprecated APIs: Runner Classes: __SwiftValue From our investigation, __SwiftValue appears to be an internal Swift runtime class automatically generated by the Swift compiler for Swift–Objective-C bridging. It is not imported, referenced, or used directly in our source code. We verified that: The symbol exists only in the compiled Runner binary It is not referenced by any third-party framework explicitly It appears in standard Swift runtime behavior We previously removed a legitimate private API (PGHostedWindow) from a dependency and resubmitted, after which this new rejection appeared. Questions: Is __SwiftValue considered a private API usage by App Review, or is this a false positive? Are there recommended build settings or mitigations to prevent this symbol from being flagged? Should this be escalated for manual review? Any guidance from Apple e