“DTiPhoneSimulatorErrorDomain Code 2”

For some reason since iOS 26.5, a ControlWidgetButton or a Button in a widget configured with an AppIntent conforming to OpenIntent fails to receive its AppEnum parameter correctly if the intent and enum are defined inside a shared Swift Package. Tapping the control widget button opens the main application, but it doesn't pass the AppEnum parameter value in, leaving the app on its default screen instead of navigating to the intended view. This was working perfectly in iOS 26.4, where the app would launch and receive the correct enum case from the intent. No code, configuration, or scheme changes were made between the two runs, only the simulator/OS version differs. Has anyone else run into what seems to be a regression on iOS 26.5? I filed feedback with a sample project: FB22848510

I’m implementing an Apple AssistiveTouch eye tracker accessory for iPad over USB-C using iAP2 plus native HID Gaze Point reports. Current state: iAP2 authentication succeeds identification succeeds StartNativeHID is received AssistiveTouchInformation(IsEnabled=true) is received iPadOS enumerates the HID interface and consumes the interrupt IN reports The remaining issue is that the gaze-point behavior is not interpreted as direct screen coordinates. Repeated fixed gaze inputs produce deterministic but incorrect cursor motion, often appearing like orbiting or projection around a locus rather than stable placement. I have tested: the 119-byte Apple example HID descriptor from the Accessory Interface Specification two report-1 layouts: timestamp + x + y status + timestamp + x + y normalized and physical coordinate scaling verified on the wire that the intended report bytes are sent and consumed iPad console logs show internal model point (HID r) values and multiple derived Pointer positions for a single

Hi, I submitted an app review appeal on May 21. It has been over 60 hours now. I'm unsure if I viewed the submission success page. No confirmation email received, and no status update in App Store Connect. App Apple ID: 1308698895 Could you please confirm: 1.Whether my appeal has been successfully received 2.The estimated time to get a reply Thanks.

My app has been for review for 2 months now , and the support team is ignoring my emails any reason this is my app id 6757392645

https://github.com/pytorch/pytorch/issues/132624 this fp8 dtypes unsupport issue has been existed for 2 years, does mlx have any plan to it?

Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified) On Intel Macs, Xcode 26.5 (build 17F42) downloads the darwin-arm64 build of the Claude Agent rather than the darwin-x64 build that the vendor publishes at the same version. The arm64 binary fails to exec on Intel with NSPOSIXErrorDomain Code=86 (Bad CPU type in executable) and Xcode's Intelligence subsystem then surfaces this in the UI as a code-signing / sandboxing failure. Replacing the downloaded binary with the parallel darwin-x64 build, and updating the agent's Info.plist checksum and URL to match, results in a fully functional Claude Agent in Xcode 26.5 on the same Intel Mac. This was verified end to end on the affected hardware. The agent downloader in Xcode should select the URL matching the host CPU architecture (e.g. by inspecting the result of uname -m or the equivalent in Foundation). This appears to be an isolated fix to which

FB22844728 Xcode 26.5, macOS 26.5, MacStudio M1 64 GB The disaster of S-L-O-W T-Y-P-I-N-G that plagued Xcode several years ago returns. I guess all the ultra-advanced LLM neuroneirowebs still can't advise those at Apple who develop the Xcode app how to provide this uber-exotic, unheard-of functionality: JUST TYPING THE CODE. This disaster doesn't affect all projects, but it does affect the exact one I'm working on, and I need to type a lot of code there. Significant time is already wasted. I performed all the recommended steps like relaunching, restarting, and deleting deprived data with no effect. Hope something can be done about it..

Apple Developer Program Enrollment — Payment Processed, Account Still Pending After 3+ Days Hello Apple Developer Support and community, I enrolled in the Apple Developer Program as an individual and my payment of $99 was successfully processed several days ago. However, my account at developer.apple.com/account still shows my enrollment as pending with no activation. Enrollment details: • Enrollment type: Individual • Payment status: Successfully charged • Time since payment: 3+ days (well past the stated 48-hour processing window) • Two-Factor Authentication: Enabled • Follow-up communication received from Apple: None I am actively developing a cross-platform application that is already in internal testing on Google Play. I need access to App Store Connect and TestFlight to begin iOS beta testing with users who are waiting. This delay is directly impacting my development timeline and my ability to gather feedback from iOS testers. I have not received any emails requesting additional documentation o

OK hello Apple developers, and whoever else is reading, I am a quadriplegic. This means I cannot use my fingers. So therefore I cannot pick up the phone. That means I cannot pick up the phone for Face ID which is biometric, fingerprint which is biometric, I believe the eye is biometric. So is the voice. That is how I have to login to my brokerage firms multiple bank account. Anything super secure I can use my voice as a password. It's super simple. Just add and the code and write it so therefore it is as simple as saying something to the effect of hey seri my voice is my password. A few simple lines of code written by Apple expert this should not be hard at all and should be included in an update. Just think how would you use your phone if you could not pick it up. I cannot put Apple Pay i cannot secure on my phone because I cannot lock it because I cannot pick it up. Any help would be greatly appreciated

Hi DTS team, We have a TestFlight build that is stuck in two ways simultaneously, suggesting a server-side state issue on the build or the account. This has now persisted for over a week with no usable response from Apple Support, so I'm escalating here in the hope of getting an engineer's attention. App: HAVN 360 Apple ID: 6769371655 Bundle ID: com.havn.member Team ID: XTRZ36RKU8 Build: 1.0.0 (1) — Binary State: Validated, status Testing, expires in 81 days SYMPTOM 1 (internal testing): Build is attached to the internal group Team (Expo) with a green check. TestFlight on iPhone (UAE storefront, account-holder's Apple ID (redacted — visible to Apple via Team ID) shows HAVN 360 with an Install button. Tapping Install returns: Could not install HAVN 360. The requested app is not available or doesn't exist. Already attempted: Removed all prior dev builds and provisioning profiles Signed out / back into Media & Purchases Full device restart Repeated after Agreements, DSA, App Privacy and Test Informa