Hi, a user of one of my apps running on his iPhone 15 with the latest iOS reports that he suddenly cannot import or export files anymore. My app allows to save and load databases from iCloud or locally on the iPhone. This is done using buttons on a main menu which are not reacting anymore for this user. He still can use buttons which trigger functions not requiring file access (like printing data from the database). So far, it is an isolated case (1 of about 500 users reporting this behaviour) but I cannot find an explanation. Has anybody ever seen something like this? Thanks for any ideas/help.

Hello there everyone. I've got numerous support projects using old school development. Things from Objective-C to RxSwift and UIKit. I've tried the LLM/Agents and they just destroy the codebase over time, so I have given up. The final straw was trying to get it to fix a POSTCODE validation issue which was using some novel ways to provide validation in place using RxSwift. Has anyone had any luck with these LLMs on Legacy codebases? Would love to hear tips.

I can run v1 of Parallax Previewer just fine, but v2 pops up an error on open. In console I can see a crash log that states that CoreRe.framework is looking for _FigSTSCreate inside the system's MediaToolbox.framework. I guess Tahoe doesn't have that. Is there a new version coming that works on Tahoe? or a workaround? I couldn't find an existing discussion about this. thanks.

Platform and Version Platform: iOS iOS Version: 17.0+ Development Environment: .NET MAUI (C#, .NET 9) Network Layer: HttpClient with HttpClientHandler Description of the Problem We are facing an issue where HttpClientHandler.ServerCertificateCustomValidationCallback is not being invoked when the app is in a terminated (kill) state. In normal app lifecycle states (foreground/background), the callback is triggered as expected and allows us to handle server certificate validation (e.g., for certificate pinning or custom validation logic). However, when the app is in a killed state and is relaunched due to a notification action, the callback does not execute. We would like to understand: Why ServerCertificateCustomValidationCallback is not invoked in this scenario Whether this behavior is expected within iOS networking/runtime constraints Any recommended approach or workaround to ensure certificate validation still occurs when handling notification-triggered flows from a terminated state Steps to Reproduce Ensure the app is force-terminated (kill mode) Configure a push notification with category: "INVITE_CATEGORY" Include custom notification action buttons Tap one of the custom actions This triggers app launch and network call using HttpClient Expected Behavior ServerCertificateCustomValidationCallback should be invoked during the network request initiated after tapping the notification action, allowing custom certificate validation.

I added a dummy view - copy paste directly from the Apple Developer Documentation, in a swift package using swift 6 and got concurency error. The fix is to switch to swift 5

Hi, anyone managed to make this work? https://developer.apple.com/documentation/backgroundassets Trying for past few days and can't make it work. Following their official documentation, also this video https://www.youtube.com/watch?v=M3jpgZrB1uo, but it seems I am stuck at: try await AssetPackManager.shared.ensureLocalAvailability(of: assetPack) What I did: Manifest files created, info.plist configured, asset pack created and uploaded to appstoreconnect via transporter, successfully assigned to app and ready for internal testing. Added to my code: let assetPack = try await AssetPackManager.shared.assetPack(withID: "Tutorial") try await AssetPackManager.shared.ensureLocalAvailability(of: assetPack) let videoData = try AssetPackManager.shared.contents(at: "Videos/Introduction.m4v") but no luck at all.... is anywhere any demo project available to download to compare with my project?

I used to develop iPhone apps about a decade ago and am now back at it with an iPhone and companion Apple Watch app. Why does it suck so bad? I a must be doing something wrong, but what I am doing is out of the box. The majority of the time when I go to build on the watch I get: Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters. Which I then first try to force quit the app on the watch and if that does not work, reboot the watch (which is pretty ridiculous). I tried Gemini and it gave me the following explanation: This is arguably the single most frustrating error in the entire watchOS development ecosystem. As an expert, I can tell you that you are not doing anything wrong; you are fighting a fragile architecture. Here is the technical breakdown of why this happens and a workflow to mitigate it without constant reboots. The Technical "Why" This error message reveals that the issue lies in the CoreDevice (and formerly usbmuxd) infrastructure, specifically in the secure transport layer. The "Tunnel" Failure: Xcode attempts to establish a secure, encrypted tunnel (DTXConnection) to the Apple Watch to push the debugger and the app binary. Unlike the iPhone, which can sustain a high-bandwidth connection easily, the Watch aggressively manages its radios (Bluetooth vs. WiFi vs. AWDL) to save battery. The "Handshake" Timeout: If the Watch is on Bluetooth (Low Energy) when Xcode initiates the tunnel, the bandwidth is insufficient. The system tries to escalate the connection to WiFi (or Apple Wireless Direct Link). If this negotiation takes even a few milliseconds too long—due to 2.4GHz interference, router mDNS configuration, or the Watch CPU being throttled—the handshake times out. The "Previous Preparation Error": This is the insidious part. Once the handshake fails once, Xcode’s device service caches that failure state for the device UUID. It marks the device as "unreachable" to prevent the IDE from hanging indefinitely on subsequent tries. Why you see it constantly: You aren't actually triggering a new connection attempt; you are hitting the cached "failed" state immediately. Unfortunately, the solutions it gives me are: The "Wired Proxy" Method (Most Reliable) This is the gold standard for watchOS debugging. Do not rely on "Connect via Network" for the Watch directly if you can avoid it. Disable WiFi on your Mac (temporarily) or ensure the Mac and iPhone are on the exact same SSID. Plug your iPhone into the Mac via USB. Ensure the Watch is paired to that iPhone. Result: Xcode will tunnel the instructions through the USB connection to the Phone, and the Phone acts as a high-bandwidth proxy to the Watch. This eliminates the "Mac-to-Watch" WiFi negotiation failure point. Do you hit this regularly? What do you do to make for a smooth development and deployment process? Or is it really this fragile? Thanks for any help! Bryan

I'm a solo developer and owner of my companies account. I'm trying to sign on to my Mac so I can use my developer account to get a certificate for wallet use and to select the correct developer account for applications in Xcode. I'm am brand new to all this so apologize if I'm missing the simple solution. I'm not able to edit the roles of my developer account but being an Admin I should already have all the necessary access...I think. I get an error when trying to logon as a work account: Searching for the long error doesn't provide a solution in the forum or through search engines. AI says to check the roles.

Hello I am trying to publish my application built through Base44 but I am struggling with one element ''Unable to Add for Review The items below are required to start the review process: You must choose a build'' I have installed XCode but I am struggling with setting the application properly. I have sent two emails to Apple Developer and been on the phone after two call back requests for nearly two hours and no response Would anyone advise how to finalise this setup and publish the app? Best wishes, Catalin

This morning my MacMini wokeup to this. CODEX was on the trash bin and every single fix suggested by ChatGPT didn't worked. If this is the result of a pissing contest between Apple and OpenAI, this is defeneteley a childish attitude and a good way to pissof developers worldwide.

Hello, I would like to have MSAL login fully working in a Developer ID signed macOS application. I am using the following library for adding MSAL support to my macOS app : https://github.com/AzureAD/microsoft-authentication-library-for-objc . The MSAL login (even silent login via the MSAL broker) works fully via my company Entra ID when I run and test my local dev build. But : when I build and sign and notarize my application with a company Developer ID signature, the login fails, and I see keychain access related issues in the MSAL library log entries. The MSAL library requires the following keychain access groups to be enabled : $(AppIdentifierPrefix)com.company.app.bundle.id $(AppIdentifierPrefix)com.microsoft.identity.universalstorage The above requirement is confirmed under these links: https://learn.microsoft.com/en-us/entra/msal/objc/howto-v2-keychain-objc?tabs=objc and also their sample app : https://github.com/AzureAD/microsoft-authentication-library-for-objc/blob/410256714ee0489d212c0cbd8772259a69e7d862/MSAL/test/app/mac/MSALMacTestApp.entitlements#L18 The problem seems to be that such keychain access groups access cannot be configured for Developer ID signed applications. Would it be possible to enable such Keychain Access groups somehow for a Developer ID signed application? Thank you for any help in advance!

I’m a registered iOS developer, and I’ve been facing an issue with installing iOS developer updates for the past couple of years. I can download the updates, but they get stuck at 99.9% complete and don’t finish. I’ve tried following the instructions to force restart the phone, but it stays on the Apple logo screen until it dies. I can update official iOS versions, but not beta versions. To update, I have to put the phone in DFU mode and install the update that way. This is frustrating and prevents me from making timely updates to my app and from diagnosing new issues during testing. I’d like to request that Apple investigate this issue and identify a solution. For reference, I’ve installed a bare-bones version with no new apps, and the problem persists. I would like a resolution that allows me to update normally without having to DFU the phone each time. This occurs via OTA or IPSW manual download and installation. Please refer to the following FB submission numbers: FB21642029 and FB21017894. CAN SOMEONE PLEASE RESPOND BACK TO THIS MESSAGE AND HELP ME TROUBLESHOOT THIS ISSUE?!

Hi everyone, I built an open-source macOS developer tool called Claude Code on OpenRouter. GitHub repo: https://github.com/allytag/Claude_Code It lets the official Claude Code CLI run through OpenRouter models while keeping the normal Claude Code workflow: tools, file editing, bash, MCP, repository work, and agent behavior. The main reason I built it is that many custom model setups break Claude Code features or make cost and model control harder. This setup keeps Claude Code itself untouched and adds a local Anthropic-compatible proxy for OpenRouter. What it does: Runs the official Claude Code CLI through OpenRouter Keeps Claude Code tools, file edits, bash, repo workflow, and MCP working Uses a local proxy at 127.0.0.1:4141 Supports model roles like main, cheapFull, hard, subagent, lowToken, backup, and compare Lets users switch OpenRouter models without reinstalling Adds cache markers and provider pinning where supported Strips reasoning fields by default to avoid hidden token cost Includes a safe updater with snapshot, validation, and rollback Includes doctor, status, cleanup, verify, uninstall, and rollback commands Avoids storing API keys in the repo Current requirements: macOS Apple Silicon Node.js 20 or newer Zsh Official Claude Code CLI OpenRouter API key Quick start: Install official Claude Code if missing: curl -fsSL https://claude.ai/install.sh | bash Clone the repo: git clone https://github.com/allytag/Claude_Code.git Claude cd Claude Preview the install: ./install.sh --dry-run Install: ./install.sh --merge Start using it: claude claude-router status Useful commands: claude-router status claude-router list claude-router tail claude-router use main deepseek-v4-pro claude-router add grok x-ai/grok-4 --name "Grok 4" claude-low "explain debounce" claude-safe-update latest --dry-run claude-safe-update latest ./verify.sh Safety details: The installer has dry-run mode before writing changes Existing Claude settings are preserved in merge mode Backups are created before changes Claude Desktop is detected but not modified The OpenRouter API key is written only to local Claude settings The repo includes a redaction check to block accidental secret commits Uninstall and restore-last-backup commands are included This is currently macOS Apple Silicon only. Linux and Windows are not supported yet because the installer uses macOS-specific paths and LaunchAgent behavior. I would appreciate feedback from other macOS developers who use AI coding tools. In particular: Does this install cleanly on your Apple Silicon Mac? Are there edge cases with Claude Code tools, MCP, or VS Code integration? Are there better defaults for model roles or safer update behavior? Is there anything I should change before calling this more stable? Repo again: https://github.com/allytag/Claude_Code Thanks.

I have my 2 apps written in .NET MAUI on the PC. I have had success deploying them to the Apple App Store from within Visual Studio. https://apps.apple.com/ie/app/the-club-referee/id6752123189 https://apps.apple.com/ie/app/the-club-fan/id6751670297 However sometimes when I go through the Compile - Publish - Distribute process I get no errors but still the app does not appear in TestFlight. Is there anyway I can see where it's failing? Is there an extension for Visual Studio that will show the errors? Can I look on my MacMini and find the deployment errors there?

HI, I have a Swift UI app in the mac appstore in the upcoming release we have made lots of changes and it is working fine in debug mode but in production with testflight or direct distribution we are getting the following crash while working in the app. this is happening in the rendering phase. Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libswiftCore.dylib 0x19546f270 swift_unknownObjectRetain + 44 1 libswiftCore.dylib 0x1954bb09c swift_cvw_initWithCopyImpl(swift::OpaqueValue*, swift::OpaqueValue*, swift::TargetMetadata<swift::InProcess> const*) + 280 2 libswiftCore.dylib 0x1958f685c initializeWithCopy for ClosedRange<>.Index + 212 3 VirtualProg 0x104d73958 <deduplicated_symbol> + 56 How can i debug to find out what is causing the issue and fix it?. thanks in advance

I have a parental control app that uses FamilyControls, ManagedSettings, and DeviceActivityMonitor across two extension targets (DeviceActivityMonitor and ShieldConfiguration). The main app target received its Family Controls (Distribution) entitlement without issue. I then submitted requests for the same entitlement for both extension targets on April 16. Both still show as "Submitted" with no update after 12 days. Two questions: What is the typical turnaround time for extension entitlement requests? The main app was approved relatively quickly. Is there anything additional required for extension targets beyond the standard request? I submitted through the normal entitlement request flow. I didn't include any supplementary documentation as none was requested. These are the last blocker for App Store submission. Any guidance appreciated.

We are reaching out to request urgent assistance with a critical issue affecting Universal Links validation for one of our production domains. The Apple App Site Association (AASA) file is now correctly served from our domain: HTTP 200 No redirects Valid JSON Correct appID and paths https://mobiledeeplink.bancogalicia.com.ar/.well-known/apple-app-site-association Despite this, Apple’s CDN endpoint still returns a 404: https://app-site-association.cdn-apple.com/a/v1/mobiledeeplink.bancogalicia.com.ar Thank you very much for your support. Best regards, Mauricio Pauluk

Looks like the Weather Kit API is down again. Anybody having the same issue?

Hello, I'm experiencing a critical issue with my Flutter iOS app on TestFlight where the app shows a completely black screen immediately after launch. The app does NOT crash (no .ips logs in iOS Settings → Analytics & Improvements), but Flutter Engine appears not to start at all. The same code runs perfectly on Android. PROJECT INFO: App Name: CNC AI Assistant Bundle ID: com.beratech.cncassistant Team ID: 958PPWZD27 Provisioning Profile UUID: 8122ca65-b15f-4daa-b0d2-1da5409c6859 Build CI: Codemagic Flutter Version: 3.41.5 iOS Deployment Target: 14.0 Test Device: iPad15,3 running iOS 26.x ISSUE BEHAVIOR: Build succeeds on Codemagic without errors IPA is signed with valid distribution certificate TestFlight processes and accepts the build Tester downloads/updates from TestFlight successfully App opens → completely BLACK SCREEN immediately LaunchScreen.storyboard does not appear App does not auto-close (must be manually killed) NO crash logs generated in iOS Settings Same exact codebase works on Android (Google Play Internal Testing) DEBUGGING ALREADY ATTEMPTED: Replaced main.dart with MINIMAL code (only Firebase init + single Scaffold with white background and Text widget) - still black screen Removed flutter_secure_storage package (had a known iOS 26 keychain init crash) - still black screen Updated IPHONEOS_DEPLOYMENT_TARGET from 13.0 to 14.0 in pbxproj to match Podfile platform - still black screen Tried both empty entitlements and entitlements matching the provisioning profile (com.apple.developer.applesignin + keychain-access-groups) - still black screen Verified GoogleService-Info.plist is registered in pbxproj Verified LaunchScreen.storyboard exists and is valid Verified Info.plist has UILaunchStoryboardName = LaunchScreen and ITSAppUsesNonExemptEncryption = false AppDelegate.swift contains only GeneratedPluginRegistrant.register PROVISIONING PROFILE ENTITLEMENTS: application-identifier: 958PPWZD27.com.beratech.cncassistant com.apple.developer.applesignin: Default keychain-access-groups: 958PPWZD27.*, com.apple.token com.apple.developer.team-identifier: 958PPWZD27 get-task-allow: false (production) INSTALLED PLUGINS (from GeneratedPluginRegistrant.m): firebase_auth, firebase_core, firebase_storage, cloud_firestore purchases_flutter, purchases_ui_flutter (RevenueCat) sign_in_with_apple, google_sign_in_ios shared_preferences_foundation, path_provider_foundation webview_flutter_wkwebview, video_player_avfoundation url_launcher_ios, image_picker_ios, file_picker permission_handler_apple, package_info_plus, device_info_plus app_links, open_filex QUESTIONS: What could cause a Flutter iOS app to silently fail to launch on iOS 26 with no crash logs? Is there a known incompatibility between iOS 26 and certain entitlement configurations? Could there be a mismatch issue between the provisioning profile entitlements and the app's actual entitlements that causes silent termination on iOS 26 specifically? How can I obtain detailed launch/crash logs from the test device when no .ips file is generated? (sysdiagnose only shows system services like BackgroundShortcutRunner, not my app) Are there any iOS 26-specific changes related to TestFlight builds or Flutter Engine initialization that I should be aware of? I have full access to: Complete pbxproj Info.plist, Runner.entitlements, Release.entitlements Codemagic build logs Generated IPA file Provisioning profile (.mobileprovision) Screenshots of black screen on test device Any guidance on diagnostic next steps or known iOS 26 issues would be greatly appreciated. Thank you in advance.

Good morning. I have an APPLE DEVELOPER ACCOUNT. I am inquiring about Distributing In House Apps using my own website. All the links so far do not help. They all seem to be relevant to the Apple Store and not In House apps. I have my apps ready for evaluation. I understand you need to evaluate them. I want to apply for a certificate that will allow me to put the apps on my OWN website and have users download these and install to their Apple devices. So far I have been testing using own devices but every build I create does NOT create a manifest file. They do work but obviously I need a manifest for the website. I assume a relevant certificate would provide that. Can you please let me know of any and all information that applies on how to apply for an In House Distribution Certificate and how and where I should upload my apps for evaluation. Thank you so much. John