Hi there, I am new to Xcode26 and dragged my AppIcon.icon (created with Icon Composer) into the project. Then build failed with "Could not locate icontool". Could anyone point me to the cleanest way to solve this? Any help would be appreciated, thanks! CompileAssetCatalogVariant thinned /Users/jaffron/Library/Developer/Xcode/DerivedData/KuuDraft-dsmpyalldiyuusdldnjihwrtzmab/Build/Intermediates.noindex/ArchiveIntermediates/KuuDraft/InstallationBuildProductsLocation/Applications/KuuDraft.app /Users/jaffron/Documents/augment-projects/WalletPin/KuuDraft/AppIcon.icon /Users/jaffron/Documents/augment-projects/WalletPin/KuuDraft/Assets.xcassets (in target 'KuuDraft' from project 'KuuDraft') cd /Users/jaffron/Documents/augment-projects/WalletPin /Applications/Xcode.app/Contents/Developer/usr/bin/actool /Users/jaffron/Documents/augment-projects/WalletPin/KuuDraft/AppIcon.icon /Users/jaffron/Documents/augment-projects/WalletPin/KuuDraft/Assets.xcassets --compile /Users/jaffron/Library/Developer/Xcode/DerivedData/KuuDraft-dsmpyalldiyuusdldnjihwrtzmab/Build/Intermediates.noindex/ArchiveIntermediates/KuuDraft/IntermediateBuildFilesPath/KuuDraft.build/Release-iphoneos/KuuDraft.build/assetcatalog_output/thinned --output-format human-readable-text --notices --warnings --export-dependency-info /Users/jaffron/Library/Developer/Xcode/DerivedData/KuuDraft-dsmpyalldiyuusdldnjihwrtzmab/Build/Intermediates.noindex/ArchiveIntermediates/KuuDraft/IntermediateBuildFilesPath/KuuDraft.build/Release-iphoneos/KuuDraft.build/assetcatalog_dependencies_thinned --output-partial-info-plist /Users/jaffron/Library/Developer/Xcode/DerivedData/KuuDraft-dsmpyalldiyuusdldnjihwrtzmab/Build/Intermediates.noindex/ArchiveIntermediates/KuuDraft/IntermediateBuildFilesPath/KuuDraft.build/Release-iphoneos/KuuDraft.build/assetcatalog_generated_info.plist_thinned --app-icon AppIcon --include-all-app-icons --compress-pngs --enable-on-demand-resources YES --development-region en --target-device iphone --minimum-deployment-target 16.0 --platform iphoneos error: unable to open dependencies file (/Users/jaffron/Library/Developer/Xcode/DerivedData/KuuDraft-dsmpyalldiyuusdldnjihwrtzmab/Build/Intermediates.noindex/ArchiveIntermediates/KuuDraft/IntermediateBuildFilesPath/KuuDraft.build/Release-iphoneos/KuuDraft.build/assetcatalog_dependencies_thinned) (in target 'KuuDraft' from project 'KuuDraft') /* com.apple.actool.notices */ warning: Could not locate icontool.

I'm suddenly receiving zero products from SKProductsRequest, even though this setup previously worked without issues. The debugger shows that both of my product identifiers are now being returned under invalidIdentifiers, and response.products is empty. I’ve confirmed the following: There are no pending agreements in App Store Connect. The subscription is active and configured correctly. The product identifiers match exactly with what’s defined in App Store Connect. Here is the delegate method I'm using (unchanged from when it previously worked): extension UpgradeViewModelProvider: SKProductsRequestDelegate { func productsRequest(_ request: SKProductsRequest, didReceive response: SKProductsResponse) { if response.products.count > 0 { delegate.send(.onProduct(response.products)) } } } Since everything was functioning before, I’m trying to understand what may have caused the identifiers to suddenly be marked as invalid. Any guidance or suggestions on what to check next would be greatly appreciated.

My iPhone 11 has iOS 18.4 Beta and my new iPhone 16e isn’t supported for iOS 18.4 Beta (for now) and is on iOS 18.3.1 Beta. If anyone knows when it’ll be supported please let me know.

Only after buying a new iPhone 16e today 3/2 did I realize I couldn’t migrate the apps on my old iPhone SE, which was running beta 18.4. Yay, Apple. Thoughtful of you to introduce new hardware when the software isn’t yet released.

The MacStudio has only one account on it, and that is of course an admin account. The password to this account is lost. The MacStudio has an association with my AppleID I log into developer.apple.com with. To recover, this procedure was followed: The recovery mode was entered by holding down the power key for 15 seconds. In the options that appeared the "Forgot all passwords" option was clicked on. I entered the same credentials I log into developer.apple.com with. The credentials were accepted. The shell was launched, and the in the shell the command "resetpasswords" entered. The message: "If you don't know the password for any user on your Mac, you can deactivate your Mac and set new passwords for all users. An internet connection will be required to reactivate your Mac". Beneath this message there was in blue text: "Deactivate Mac". I did not proceed after this because I was not sure what deactivation would mean for the files on the computer. On it there is code written in Swift that needs to be preserved. If the deactivation is done will the files be preserved, and be accessible? Or does a deactivation remove all files?

Hello developers, i have a project for SSC that includes metal shader code. The project runs fine when I build and run it in Xcode, but it does not run in the Swift Playground app. The reason is that Swift Playgrounds doesn’t compile/build source files with the .metal extension the same way Xcode does (so the shader never gets built/loaded in Playgrounds). The requirements say: “Your app playground must be built with and run on Swift Playgrounds 4.6 or Xcode 26, or later.” Since it says “or” (not “and”), does that mean it’s acceptable if the project only builds/runs in Xcode?

I have been a galaxy user my whole life, I just switched over to IPhone, because of how much i see the users enjoy it. With that’s said, I make journal entries often in my phone, I would like to know if it is protected from AI usage, as these are my personal thoughts and feelings?

Apologies if this is the wrong place, I'm trying to enroll as a developer with my company. A long time ago I was invited to join, but had let the invitation expire. I'm working with my manager to try and get another email sent out inviting me into the program, but I'm not receiving anything in my inbox. Is there a known bug here? Is there something else that needs to be done to send out a second invite?

I’ve encountered a critical issue in macOS Tahoe (Beta) that affects the Photos app or any app that leverages Apple’s editing frameworks. After editing certain photos—whether applying filters, cropping, or making basic adjustments—the image suddenly turns completely black upon saving or exiting the edit mode. Details: macOS Version: macOS Tahoe (latest beta) Affected App(s): Photos, Preview, and some third-party editing apps Steps to Reproduce: Open a photo in the Photos app Make any basic edit (e.g., crop, adjust brightness) Click “Done” The edited photo appears entirely black Notes: Happens with both JPEG and HEIC formats Original photo appears fine before editing Exporting the photo also results in a black image Restarting the app/system does not resolve the issue iCloud Photos is enabled This issue seems related to the image rendering pipeline post-editing, possibly tied to Core Image or GPU rendering frameworks. It severely affects photo usability and could result in permanent data loss if backups are not maintained. Please advise if a workaround exists or if this bug has been logged already. Happy to provide system logs or sample images if needed.

Every broke I either open mail or the safari application they crash and eveytime I hit reopen and they crash again macOS 26 developer beta 2

We’re integrating Sign in with Apple using Apple’s official JavaScript SDK: https://appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js We’ve successfully used this setup with an older Service ID, but when we try to use any newly created Service ID, we get the following error immediately when calling AppleID.auth.signIn(): invalid_client This happens before any request reaches our backend. The same flow, redirect URI, and frontend code works fine with an old Service ID — but fails with new ones. ✅ What We’ve Verified: The Service ID (e.g., com.projectx.web.login) is created under Apple Developer → Identifiers → Service IDs The redirect URI is correct and matches exactly (HTTPS, no trailing slash) No client_secret is passed in the frontend (by design) We’re using usePopup: true ❌ What Doesn’t Work: Any new Service ID we create — even on the same domain and configuration — fails with invalid_client. 🔁 What We’ve Tried: Creating multiple new Service IDs Waiting 48+ hours in case of propagation delays Validating HTTPS and redirect URI setup Comparing all settings with the working (older) Service ID (which we deleted since we thought that was causing a problem) Testing in different environments and browsers ❓ Questions: Why do newly created Service IDs fail with invalid_client while older ones work? Are there undocumented requirements, propagation delays, or steps for new Service IDs to become active? Is this a known limitation or bug in the SDK? 💻 Our Code: import { useEffect } from "react"; import { Button, Box } from "@mui/material"; import api from "../utils/api"; // Axios wrapper import AppleIcon from "@mui/icons-material/Apple"; import MainAuthStyles from "../pages/MainAuthStyles"; import { useUser } from "../../../user-module/src/contexts/UserContext"; import { useNavigate } from "react-router-dom"; // Apple global type declare global { interface Window { AppleID: any; } } type AppleSignInButtonProps = { setApiError: (msg: string) => void; }; const AppleLogInButton = ({ setApiError }: AppleSignInButtonProps) => { const { user, setUser } = useUser(); const navigate = useNavigate(); useEffect(() => { if (!window.AppleID) return; window.AppleID.auth.init({ clientId: import.meta.env.VITE_APPLE_CLIENT_ID, scope: "name email", redirectURI: import.meta.env.VITE_APPLE_REDIRECT_URI, usePopup: true, }); }, []); const handleAppleLogin = async () => { try { const response = await window.AppleID.auth.signIn(); const { id_token, code, user } = response.authorization; const res = await api.post("/auth/apple-login", { idToken: id_token, code, user, rememberMe: true, }); if (res.data.success == true && res.data.user.userDataInitialised == true ) { setUser({ id: res.data.user.id ? res.data.user.id : '', fullName: res.data.user.fullName ? res.data.user.fullName : '', email: res.data.user.email ? res.data.user.email : '', role: res.data.user.role ? res.data.user.role : '', signUpType: res.data.user.signUpType ? res.data.user.signUpType : '', userDataInitialised: res.data.user.userDataInitialised ? res.data.user.userDataInitialised : false, }); localStorage.setItem("accessToken", res.data.accessToken); localStorage.setItem("refreshToken", res.data.refreshToken); navigate("/app") } else { setApiError("Unrecognized login method") return; } } catch (err) { console.error("Apple Sign-In failed", err); setApiError("AppleSignInFailed"); } }; return ( <Box mt={2}> <Button variant="outlined" fullWidth onClick={handleAppleLogin} className="AuthAppleButton" startIcon={<AppleIcon />} > Log in with Apple </Button> </Box> ); }; export default AppleLogInButton; Any help from the Apple team or anyone who's resolved this issue would be appreciated — we’re currently blocked on deploying new environments due to this error. Thanks!

I am implementing BLE scanning and connection using CoreBluetooth in a Flutter application with native iOS Swift code. BLE scanning and connection work correctly in the foreground and for a short time after the app is sent to the background. However, after some time in the background, BLE scanning stops and the device is no longer discovered. The app appears to be suspended by iOS. Key Observation: When location services are actively in use (navigation arrow visible in the iOS status bar), BLE scanning and reconnection work reliably in the background. When location services are not actively running, BLE scanning stops in the background even though the app has “Always Allow” location permission. Expected Result BLE scanning and connection should continue to function in the background using the Bluetooth LE background mode, without relying on active location updates. Actual Result BLE scanning starts successfully App enters background After some time, scanning stops Device is no longer discovered BLE works again only if location services are actively running BLE Connection Behavior One-time scan connects successfully to a BLE medical device App is sent to background Existing connection does not disconnect However, new scans or reconnections fail once the app is suspended Relevant Native iOS Code (AppDelegate) import Flutter import UIKit import CoreBluetooth @main @objc class AppDelegate: FlutterAppDelegate { private var backgroundTaskID: UIBackgroundTaskIdentifier = .invalid override func application( _ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? ) -> Bool { GeneratedPluginRegistrant.register(with: self) if let identifiers = launchOptions?[UIApplication.LaunchOptionsKey.bluetoothCentrals] as? [String] { print("App relaunched for BLE state restoration: \(identifiers)") } NotificationCenter.default.addObserver( self, selector: #selector(appDidEnterBackground), name: UIApplication.didEnterBackgroundNotification, object: nil ) return super.application(application, didFinishLaunchingWithOptions: launchOptions) } @objc private func appDidEnterBackground() { backgroundTaskID = UIApplication.shared.beginBackgroundTask { self.endBackgroundTask() } } private func endBackgroundTask() { if backgroundTaskID != .invalid { UIApplication.shared.endBackgroundTask(backgroundTaskID) backgroundTaskID = .invalid } } } Questions for DTS: Is it expected behavior that CoreBluetooth background scanning effectively stops once the app is suspended, even when the Bluetooth LE background mode is enabled? Why does BLE background scanning appear to work reliably only when location services are actively running? Is iOS internally associating BLE background execution with active location updates? For continuous BLE reconnection (medical device use case), is the recommended approach to rely solely on CoreBluetooth state restoration instead of continuous background scanning? Is it considered best practice to avoid long-running BLE scans in the background and instead wait for system-delivered BLE events? Additional Notes Issue is reproducible on real devices Not using private APIs or unsupported background execution methods Objective is to follow Apple-recommended, App Store–compliant behavior

I've got the initial WWDC beta of macOS 26 (25A5279m) installed inside a virtual machine (UTM), but can't seem to update to the second beta. Nothing is showing up within Software Update. Is this because it's within a VM, or am I doing something wrong? It'd be a real pain to have to install a new VM afresh with the RestoreImage for every update.

Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design, hoping for the best. Thanks. My FB-FB18327769

For the SSDC submission, the app playground must run on Swift Playgrounds 4.5+ or Xcode 16+. Key questions: In Swift Playgrounds, is the app tested on iPadOS or macOS? In Xcode 16+, is the playground tested using Mac Catalyst, an iPad simulator, or an iPhone simulator? The submission form only mentions a simulator but doesn’t specify which one. Can I build an app primarily for iPhone (portrait mode), or is it better to focus on iPad (landscape mode) if that’s the expected testing environment in all cases?

Hi,Does anyone else encountered a delayed or unresponsive change when trying to change input languageon macos Sierra?Beta1 and 2 same problem.Working great on El Capitan.Thanks in advanced

We are currently facing an issue with implementing "Sign in with Apple" in our iOS application built using Flutter. We've implemented "Sign in with Apple" using Firebase and On attempting to sign in, we are encountering the following error: “Sign-up not completed.” We have verified that: The Apple Sign is enabled on our Firebase Project. The Sign in with Apple capability is enabled in the Xcode project. The Apple Sign-In capability is enabled for the App ID on our Apple Developer account. All the certificates were re-provisioned after enabling the capability. The Bundle ID matches across Apple Developer portal and our app configuration. The email and fullName scopes are requested in the credential. Please let us know if you require any additional information. We’re happy to provide whatever is needed. Here's a screenshot attached to explain the problem better

Hey everyone, First time posting on here. I updated my iPhone 15Pro to 18.4 this morning march 5th, and almost immediately my phone started bugging. Safari won’t load, neither will some of my apps that are heavily data based like Mail. I tried WiFi and data, no difference, I tried different WiFi connections and even a hotspot. Siri and chatGPT also won’t load BUT instagram, Snapchat, TikTok, X, and threads are working perfectly fine. Most games won’t load either. I tried to use a VPN and it has allowed me to access everything that is down Including Siri. This is a temporary solution, hopefully there is a more permanent fix. Thank you all in advance.

Hi everyone, I’m developing an app for managing internet services, which includes features like controlling modems, paying internet bills, purchasing internet packages, buying cameras, subscribing to FSafety (modem management), UltraFast (boosting internet speed for gaming), and selling health-related devices like blood glucose monitors, as well as other telecom-related products. I have some questions about Apple’s review process and payment policies: Do features like paying internet bills, buying internet packages, purchasing cameras, subscribing to FSafety and UltraFast violate any of Apple’s policies (App Store Review Guidelines)? If my app doesn’t violate any policies, how would Apple charge for these transactions, and what is the fee structure? If I use an external payment gateway (not Apple’s) for transactions like paying bills or buying products, would I need to provide additional documentation for my app to be approved on the App Store? What is the review process for apps with external payment features? Is there anything special I need to do when submitting the app to the App Store? I would appreciate any insights from those who have experience with developing apps that include payment functionality. Thanks so much!

hi team To continue testing Xcode 26 beta for our POS project's compatibility with the upcoming iOS 26 release in September, we’ve been running trials on various simulators. While the app works fine on iOS 18 simulators (iPad Pro/Air), it fails to launch on iOS 26-based iPad simulators with the following error: "libswiftWebKit.dylib library is not loaded"...... SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib (Detailed logs are shared below.) Is there a known fix for this issue, or is a resolution expected in an upcoming beta release? dyld[34660]: Library not loaded: /usr/lib/swift/libswiftWebKit.dylib Referenced from: <BA066DAA-6AD6-3622-9A40-08C1600B0DC6> /Users/username/Library/Developer/CoreSimulator/Devices/3F807800-D684-4398-89DC-1AEC1747A99A/data/Containers/Bundle/Application/5327A260-4241-48F6-85C2-A7E0E0F152E3/Projectname.app/Frameworks/SquareReaderSDK.framework/SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftWebKit.dylib' (no such file), '/usr/lib/swift/libswiftWebKit.dylib' (no such file, not in dyld cache), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libswiftWebKit.dylib' (no such file) Library not loaded: /usr/lib/swift/libswiftWebKit.dylib Referenced from: <BA066DAA-6AD6-3622-9A40-08C1600B0DC6> /Users/username/Library/Developer/CoreSimulator/Devices/3F807800-D684-4398-89DC-1AEC1747A99A/data/Containers/Bundle/Application/5327A260-4241-48F6-85C2-A7E0E0F152E3/Projectname.app/Frameworks/SquareReaderSDK.framework/SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftWebKit.dylib' (no such file), '/usr/lib/swift/libswiftWebKit.dylib' (no such dyld config: DYLD_SHARED_CACHE_DIR=/Library/Developer/CoreSimulator/Caches/dyld/24F74/com.apple.CoreSimulator.SimRuntime.iOS-26-0.23A5260l/ DYLD_ROOT_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libLogRedirect.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libBacktraceRecording.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libViewDebuggerSupport.dylib DYLD_FRAMEWORK_PATH=/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator DYLD_FALLBACK_FRAMEWORK_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks DYLD_FALLBACK_LIBRARY_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib```