An Administrator account is executing safaridriver --enable but it doesn't apply to other standard user accounts and standard accounts can't enable it directly. Is this expected behavior? How can standard users make use of safaridriver?

Context I trained a LoRA adapter for Apple’s on-device language model using the Foundation Models Adapter Training Toolkit v0.2.0 on macOS 26 beta 4. Although training completes successfully, loading the resulting .fmadapter package fails with: Adapter is not compatible with the current system base model. What I’ve Observed, Hard-coded Signature: In export/constants.py, the toolkit sets, BASE_SIGNATURE = "9799725ff8e851184037110b422d891ad3b92ec1" Metadata Injection: The export_fmadapter.py script writes this value into the adapter’s metadata: self_dict[MetadataKeys.BASE_SIGNATURE] = BASE_SIGNATURE Compatibility Check: At runtime, the Foundation Models framework compares the adapter’s baseModelSignature against the OS’s system model signature, and reports compatibleAdapterNotFound if they don’t match—without revealing the expected signature. Questions Signature Generation - What exactly does the toolkit hash to derive BASE_SIGNATURE? Is it a straight SHA-1 of base-model.pt, or is there an additional transformation? Recomputing for Beta 4 - Is there a way to locally compute the correct signature for the macOS 26 beta 4 system model? Toolkit Updates - Will Apple release Adapter Training Toolkit v0.3.0 with an updated BASE_SIGNATURE for beta 4, or is there an alternative workaround to generate it myself? Any guidance on how the Foundation Models framework derives and verifies the base model signature—or how to regenerate it for beta 4—would be greatly appreciated.

My app uses VStack and HStack, instead of the normal table format. When I try to print everything works perfect but it will not print the cell outline. What is the correct line code or instruction terminology? Thanks, Hal

I'm experiencing a specific issue where when using any of the MacOS 26 Tahoe betas with Low Power Mode enabled and using Vsync in fullscreen, my application framerate gets limited to a hard 30 fps. I have not experienced this on any older OS. For example Low Power Mode on 13.6 Ventura with Vsync fullscreen lets my application run at full 60 fps without issues. Is this a bug or a change in behavior of Low Power Mode on Tahoe? My application is 3D, runs at 60 fps and is sensitive to tearing, so I need Vsync and it is mostly utilized in fullscreen. And Low Power Mode is a default for many Macs, so default experience on Tahoe currently is a halved 30 fps. However there also seems to be inconsistencies of on which machines this happens, but older OSes are always fine.

We executed the iOS package using UE5.5 on Windows. UE automatically launched the "Metal Developer Tools for Windows". I tried two versions, 5.3 and 4.4. I found that the metal.exe sometimes had no response or output was empty. The problem of no response could be alleviated by adding timeout retries, but the problem of empty output seemed to have no effect with retries. The actual command line called was: metal.exe -v --target=air64-apple-darwin18.7.0. UE relies on this output to determine the version number, and if it cannot get it, it will crash directly. During our replication test, we used a Python script to run multiple concurrent executions of the command "metal.exe -v --target=air64-apple-darwin18.7.0". On different Windows machines, it would get stuck at a certain concurrency level. Some machines even got stuck when running two tasks concurrently. We would like to ask for solutions or available versions.

I’ve noticed that Xcode keeps automatically adding unnecessary inputPaths and outputPaths entries to my project.pbxproj file. These outputPaths don’t seem to serve any real purpose in my project and clutter the project file, sometimes causing unnecessary merge conflicts in version control. I’ve already checked I didn't change my project.pbxproj file, but Xcode still occasionally generates these outputPaths. I’m not using any custom build tools or plugins that should be modifying this. One thing I’ve observed is that this issue only occurs when Xcode is open. If I close Xcode, the problem does not happen. This makes me think it might be related to how Xcode manages or updates the project file in the background. My questions: Is there a way to completely disable Xcode from generating these outputPaths automatically? Are there any hidden settings, project configurations, or best practices to prevent this behavior? Has anyone else experienced this issue, and how did you resolve it? Any advice or insight would be greatly appreciated. Thank you!

This bundle is invalid. The IPA format requires a top-level directory named Payload, containing only a .app bundle and optional plugins in a Plugins directory. (ID: df59dbe4-17e5-4bc6-9c69-8645672320(4))

After updating to Xcode 26 Beta 4, I can no longer upload my app to App Store Connect due to a WatchKit icon validation error. The error states: Invalid Icon. The watch application 'YourApp.app/Watch/YourWatchApp.app' contains an icon file 'Icon Image-AppIcon-watch-1024x1024 @1x.png' with an alpha channel. Icons should not have an alpha channel. • This file name doesn’t exist in the asset catalog or project source. • All icon assets used in the Watch App’s AppIcon set, including the required 1024x1024 icon, were checked with sips -g hasAlpha and confirmed to not contain an alpha channel. • Project was cleaned, derived data cleared, and archive recreated multiple times. • This issue only began after updating to Xcode 26 Beta 4. In the previous versions, everything was ok. Is anyone else experiencing this after upgrading Xcode to Beta 4? Any idea/workaround on how to solve this would be appreciated.

I'm an indie developer and I'm managing my builds using xcode scm (git repo) and with github. I'm at a stage when I have to work on two different things at once on my project... Enhancements Feature change At a later stage I might want the enhancements and not the feature changes, or keep both. How should I - branch, merge and/or cherry pick on the current main branch since the Initial commit?

Good day everyone. I have a react native app which works on dev mode on my device - Iphone 13 pro version: 18.5, but when deployed to TestFlight and installed on same device it crashes when ever I click on any TextInput. I downloaded the crash file but finding it difficult to pinpoint the problem. I want to know what the problem is, if it's related to an installed package or code base or any other. Any help will be appreciated!!! Thanks. crashlog.crash

When I build the app, a block symbol appears on the app icon in the Debug Area at the bottom. What is the reason for this?

Hello Apple Developers, I'm currently working on building a custom HomeKit Accessory using the HomeKit ADK v6.3 and running the Remote.OpenSSL sample on a Raspberry Pi 4 (64-bit Ubuntu / Linux Kernel 6.1.21-v8+). I'm trying to pair the accessory via the MFi HomeKit ADK pairing process. I've successfully compiled the ADK using: The application (Remote.OpenSSL) launches correctly, and the accessory server starts as expected, broadcasting via mDNS. However, when I attempt to initiate pairing via iOS (or simulate pairing), the following error occurs: Fault fatal error - HAPPlatformAccessorySetupLoadSetupInfo @ PAL/Linux/HAPPlatformAccessorySetup.c:93 This causes the application to crash.

Hello Apple App Review Team, We are using Privy to enable sign in with Farcaster in our app. Privy is a 3rd party authentication SDK, and it currently opens the authentication URL using the system browser. Unfortunately, this behavior is handled internally by Privy and we do not have access or control to override it in order to present the sign-in flow in-app using SFSafariViewController. We understand the importance of maintaining a seamless and secure user experience, and we fully support the use of SFSafariViewController or ASWebAuthenticationSession. However, since Privy does not expose an option to change this behavior at the moment, we are limited by their current implementation. We have reached out to the Privy team requesting a change or improvement that would allow us to use SFSafariViewController instead of the external browser. In the meantime, we would appreciate your guidance on how to proceed, or whether an exception could be granted due to this 3rd party SDK limitation. Thank you for your understanding and support.

I've got an app that uses WebRTC. When I try to upload it using Xcode I get the following error: Validation failed The app references non-public selectors in Payload/{MyApp}.app/{MyApp}: initWithURLStrings: (ID: 61a6dbe5-dac2-4910-a836-b4b9b2e891b4) This API is not private, it's just unfortunate that WebRTC chose to use this name as well, and it is falsely identified as a private API by Apple. Has anyone seen this? The funny thing is, I have the exact same app with different configuration in TestFlight internal only for staging, and I could upload it without any issues. And yes, I've tried uploading this app for test flight internal only. No success either.

Hello, my name is Natalia, I'm Ukrainian. Please tell me how to contact Apple to propose a new development? It's more about a startup.

post update to beta latest update, call app crashes and unable to view, check who called and unable to save contacts. It crashes as I try to open this. It’s becoming a problem now as unable to make call. Already tried settings reset, reboot. Can you provide a solution please?

My apple app rejected on 9 of July 2025 but I didn't recieve any confirmation on mail can you please provide any written confirmation why my mail is not approved with all possibe conditions.

My notarization submission been "In Progress" status for over 30 minutes now. I thought this process should be much faster.

Hello Engineers My app was rejected with the message below, BUT I don't have this entitlements in my project! I already removed all Xcode files under ${HOME}/Developer/Xcode, but the problem still alive! Guideline 2.4.5(i) - Performance In order to continue reviewing your app, we require additional information. Your app uses one or more entitlements which do not appear to have matching functionality within the app. Please reply to this message in App Store Connect and describe how and where the app uses the following entitlements. You will not need to upload a new binary to provide this information. Apps should have only the minimum set of entitlements necessary for the app to function properly. If there are entitlements that are not needed, please remove them and submit an updated binary. You will need to Developer Reject the app to upload an updated version. "com.apple.security.assets.pictures.read-write" "com.apple.security.assets.movies.read-write" "com.apple.security.assets.music.read-write" "com.apple.security.files.downloads.read-write" Here my entitlements: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>com.apple.security.app-sandbox</key> <true/> <key>com.apple.security.application-groups</key> <array> <string>group.org.eof.apps</string> </array> <key>com.apple.security.files.user-selected.read-write</key> <true/> </dict> </plist> code-block Who or where are these entitlements inserted? Which button should be clicked to deactivate them? Link to my project: DRFXBuilder Regards

ISSUE SUMMARY: iOS app receives "The app contains one or more corrupted binaries" error during Apple's SPI (Static Program Interface) analysis after successful upload to App Store Connect. Exhaustive systematic debugging indicates this is an Apple validation infrastructure issue, not application code. ERROR IDs ENCOUNTERED: f3de06b6-6a60-45a2-9856-77327004a64e 386f96fc-851f-42ec-91d7-c77b590ffeb6 ae1a9f9a-b980-490f-ad61-27f4552a4346 3e3c1839-f3f5-4f7b-9221-659dda8de970 COMPREHENSIVE DEBUGGING PERFORMED: PHASE 1: INITIAL TROUBLESHOOTING ✅ Attempted upload without manual IPA modifications - STILL FAILS ✅ Tested with Xcode Cloud builds (Apple's own infrastructure) - STILL FAILS ✅ Tried different upload methods (Xcode Organizer, Transporter) - STILL FAILS PHASE 2: CONFIGURATION FIXES ✅ Removed all iOS 26 references from codebase - STILL FAILS ✅ Fixed missing NSPhotoLibraryUsageDescription in Info.plist - STILL FAILS ✅ Removed empty entitlements file - STILL FAILS ✅ Verified all build settings and code signing - STILL FAILS PHASE 3: SYSTEMATIC COMPONENT ISOLATION Created blank test project and tested individual components: ✅ GRDB 7.5.0 package alone - PASSES validation ✅ Supabase 2.30.1 package alone - PASSES validation ✅ RevenueCat 5.32.0 package alone - PASSES validation ✅ PostHog 3.28.3 package alone - PASSES validation ✅ airports.db database file alone - PASSES validation ✅ HTML template files alone - PASSES validation ✅ CLAUDE.md documentation file alone - PASSES validation ✅ Localizable.strings files alone - PASSES validation ✅ ALL COMPONENTS TOGETHER in test project - PASSES validation PHASE 4: CODE AUDIT AND FIXES ✅ Comprehensive multi-agent code audit identified potential issues: Fixed threading deadlock in AppContext.swift (removed DispatchQueue.main.sync) Eliminated UIPrintPageRenderer KVC usage (replaced with UIGraphicsPDFRenderer) Verified no private API usage throughout codebase ✅ Applied all fixes - STILL FAILS validation PHASE 5: COMPLETE PROJECT RECREATION ✅ Copied ALL source code from failing project to working test project ✅ Same dependencies, same resources, same configuration ✅ Test project with individual components: PASSES validation ✅ Test project with complete source code: FAILS validation with identical error PHASE 6: FINAL COMPREHENSIVE AUDIT ✅ 4 specialized code audits completed: Runtime & Reflection analysis: CLEAN String-based API & KVC analysis: CLEAN System Integration analysis: CLEAN Constants & Private Values analysis: CLEAN ✅ No violations of Apple guidelines detected ✅ No private API usage found ✅ No dangerous code patterns identified DEFINITIVE EVIDENCE OF INFRASTRUCTURE ISSUE: Every individual component passes Apple SPI analysis when tested alone All components together in test project pass Apple SPI analysis Complete source code fails Apple SPI analysis with identical error Both local builds and Xcode Cloud builds fail identically Comprehensive code audits find no violations whatsoever Issue persists across different projects, build environments, and upload methods REPRODUCTION STEPS: Archive complete iOS app using Xcode 16.4.0 Upload to App Store Connect (upload succeeds) Apple's automated SPI analysis runs Validation fails with "corrupted binary" error EXPECTED BEHAVIOR: App should pass SPI analysis as systematic testing proves all components are individually valid. ACTUAL BEHAVIOR: SPI analysis consistently reports "corrupted binary" despite exhaustive debugging showing clean code. TECHNICAL DETAILS: Bundle ID: [your bundle ID] Target: iOS 18+ Xcode: 16.4.0 Architecture: arm64 Dependencies: GRDB 7.5.0, Supabase 2.30.1, RevenueCat 5.32.0, PostHog 3.28.3 SwiftUI app with @Observable pattern Offline-first SQLite + cloud sync architecture CONCLUSION: This level of systematic debugging definitively isolates the issue to Apple's SPI analysis infrastructure. No reasonable code-level explanation remains for why individual components pass validation but the complete app fails with identical errors across multiple build environments. Requesting urgent investigation of SPI analysis validation logic that may be incorrectly flagging legitimate applications as having "corrupted binaries."