As subject, after update to Xcode 26.0.1, none of the simulator able to download, tried click the Get button, tried run command in terminal, all failed. Error from terminal: xcodebuild -downloadPlatform iOS Finding content... Automatically resolved architecture variant for platform iOS as 'universal'. 2025-10-09 06:21:24.423 xcodebuild[1789:30064] DVTDownloadable: Download Failed. Downloadable: { architectures = ( arm64, x86_64 ); authentication = none; category = simulator; contentType = cryptexDiskImage; dictionaryVersion = 2; downloadMethod = mobileAsset; fileSize = 10066611438; identifier = com.apple.dmg.iPhoneSimulatorSDK26_0; isInternalContent = 0; isUserInitiated = 1; name = iOS 26.0 Universal Simulator (23A343); patchableFrom = ( ); platform = com.apple.platform.iphoneos; simulatorVersion = { buildUpdate = 23A343; version = 26.0; }; version = 26.0.0.0; }. Download failed. Any idea how to resolve this? iMac with Intel processor
Search results for
Visual Studio Maui IOS
105,639 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
So, first off, there are two critical details I need to clarify: Note in MAC OS everything (same DExt and UserClient-code) works fine in the background and in the foreground. macOS doesn't implement any of the app suspension semantics iPadOS does, which means you can't really compare the behavior of the two systems. That leads to here: 1 variation A) UserClientApp has attribute [Background modes][Enable external communications]. The external-accessory background mode is totally unrelated to DriverKit and isn't actually doing anything in your app. It allows apps using the ExternalAccessory framework to communicate with their accessory in the background, but that framework (iOS 3.0) and the background mode (iOS 4.0) are MUCH older than DriverKit. Making this as explicit as possible: B) A way to pursue Apple-store to accept (without MFI) an UserClientApp with [Enable external communication]. ...adding external-accessory is not changing ANYTHING about how your app wakes/sleep in the background.
Topic:
App & System Services
SubTopic:
Drivers
Tags:
Thanks for the post, this is very interesting, how you tried by providing the path to download the file? xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26 Let me know what error you get. Albert Pascual
Worldwide Developer Relations.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Apps crash on launch when using View.navigationLinkIndicatorVisibility(_:) (which is iOS 17.0+ iPadOS 17.0+ Mac Catalyst 17.0+). Catalyst also crashes. Stack trace starts with: Symbol not found: _$s7SwiftUI17EnvironmentValuesV33_navigationIndicatorVisibilityABIAA0G0OvpMV Xcode 26.0.1 (17A400) iPadOS 18.3.1 (22D8075) It also crashed a user on iOS 18.6.2 macOS 15.6.1 (24G90) FB20596543 import SwiftUI @main struct NavLinkDisabledApp: App { var body: some Scene { WindowGroup { NavigationStack { List { NavigationLink(Text) {} .navigationLinkIndicatorVisibility(.hidden) } } } } }
Thank you for your post. I have a few questions. Is that your application, Zeon Charging? You also mentioned that the bug appears on the iPhone 14 with iOS 16.0.1 but does not occur on the iPhone 16 with the same version of iOS. Have you tested the latest beta version of iOS? The crucial aspect is that the same version of iOS is experiencing the issue, but the iPhone model is different. Is that correct? Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
Worldwide Developer Relations.
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
I am experiencing an issue with the CarPlay POI template in my CarPlay application. On my iPhone 14 running iOS 26.0.1, the clustering of POIs on the CarPlay map is not displaying at all. However, this issue only affects this specific model and OS version. The same app works correctly on an iPhone 14 with iOS 18.5 and on an iPhone 16 Pro Max with iOS 26.0.1. There are no code changes between builds for each device.
Since the latest Xcode has become available users in our environment are seeing this error any time they try to launch a simulator (Primarily iOS devices, but others provided the same error) We have tested on 16.4 and 26.0.1 with various suggested fixes including uninstalling and reinstalling all of Xcode. Nothing has helped.
I'm reporting a critical Health data synchronization failure that began immediately after updating from watchOS 18 to watchOS 26.0.2 (stable release) and persists in watchOS 26.1 beta 2. Bug Description: Complete failure of Health data sync from Apple Watch to iPhone Health app. All health metrics are being captured and stored locally on the watch but fail to sync to the paired iPhone. Affected Data Types: Activity rings (Move, Exercise, Stand) Heart rate measurements Sleep tracking data Workout data All other HealthKit data points Environment: Device: Apple Watch Series 7 Initial failure: watchOS 26.0.2 (23R362) - stable release Current: watchOS 26.1 beta 2 (23S5052c) Paired iPhone: iPhone 17 Pro Max, iOS 26.1 beta 2 (23B5052c) Bluetooth and Wi-Fi connectivity: Normal Watch pairing status: Connected and functional for all other features Reproduction: Updated Apple Watch Series 7 from watchOS 18 to watchOS 26.0.2 on September 30, 2025 Health data sync ceased completely starting October 1, 2025 Issue
Here's an sample code that can produce the problem. It happens on rotate in simulator, only in iOS 26.* Expectation: should have the same lead spacing regardless of the rotation of the device. struct ContentView: View { @State private var showingSharePopover = false var body: some View { NavigationStack { VStack { Button { showingSharePopover = true } label: { Label(Show Share Options, systemImage: square.and.arrow.up) .font(.title2) .padding(.vertical, 10) .padding(.horizontal, 20) } .buttonStyle(.borderedProminent) .tint(.indigo) .controlSize(.large) .shadow(radius: 5) .sheet(isPresented: $showingSharePopover, content: { }) } .navigationBarBackButtonHidden(false) .toolbar { ToolbarItem(placement: .topBarLeading) { Button { } label: { HStack { Image(systemName: square.and.arrow.left) Text(Done) } } } } .padding() } } }
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
I received this message when trying to submit a build using Rork.com. Can anyone tell me what this is and how to fix it? There is a problem with the request entity - You are not allowed to create 'iOS' profile with App ID 'XXXXXXXX'. ✖ Failed to create Apple provisioning profile Error: build command failed.
Topic:
Developer Tools & Services
SubTopic:
General
I'm on a MacBook Air 2025 M4 (Apple Silicon) using Flutter 3.35.5 on channel stable, Xcode 26.0.1, and CocoaPods 1.16.2. Actual Setup: Component Version macOS 15.0 Sequoia CPU Apple M4 (ARM64) Flutter 3.35.5 on channel stable Dart 3.9.2 DevTools 2.48.0 CocoaPods 1.16.2 Xcode 26.0.1 Build 17A400 Since updating Flutter from 3.24 → 3.35, iOS builds consistently fail with the following errors (not matter if simulation or real device, also ios version no matter): fatal error: 'Flutter/Flutter.h' file not found Error logs: /Users/myuser/.pub-cache/hosted/pub.dev/app_links-6.4.1/ios/app_links/Sources/app_links/AppLinksIosPlugin.swift /Users/myuser/.pub-cache/hosted/pub.dev/app_links-6.4.1/ios/app_links/Sources/app_links/AppLinksIosPlugin.swift:1:8 Unable to find module dependency: 'Flutter' import Flutter ^ flutter_native_splash /Users/myuser/.pub-cache/hosted/pub.dev/flutter_native_splash-2.4.6/ios/flutter_native_splash/Sources/flutter_native_splash/include/flutter_nativ
Just got the bug while listening music and started my stopwatch. Now what’s interesting is when i continuously opened the music app music is in play mode. when opening ChatGPT it stops the music. I don’t understand why but its quite annoying.
Feedback number: FB20451665 When building with Xcode 26, Voice Over is reporting an extra tab when swiping through tabs. Please see the sample project below: /* This is a Sample project to show that I believe there is a Voice Over bug in iOS 26. When swiping through tabs with Voice Over active, there always appears to be an extra tab. Here I have 5 tabs, when on tab one VO reads out tab 1 of 6, then tab 2 of 6, all the way to the last tab, when voice over reads out tab 5 of 6. Never tab 6 of 6. Is there a possibility that voice over is picking up the underlying `more` tab and reading that out? This has also been reportedly found in the Files app here: https://www.applevis.com/comment/195441#comment-195441 */ struct ContentView: View { var body: some View { TabView { /// Activating this has Voice over telling us there are 6 Tabs. Tab(RootTab.home.title, systemImage: circle.fill) { Text(This is the (RootTab.home.title.capitalized) screen) } .accessibilityLabel((RootTab.home.title.capitalized) tab) .acc
Hello, I’m developing a HealthKit-based fitness app in React Native that observes step count changes and uploads the latest totals to a remote server. I’m currently using HKObserverQuery with background delivery enabled (enableBackgroundDelivery(for:frequency:.immediate)), and the behavior works correctly while the app is running in the background or foreground. Whenever new step data is written to HealthKit, the app wakes up, reads the latest data, and sends it to my HTTPS endpoint using URLSession.shared.dataTask inside the observer callback. However, I’ve noticed the following issue: 1. If the user swipes up (force-quits) the app from the app switcher, the observer queries stop firing entirely. 2. In this state, even though HealthKit continues collecting step data from the device or Apple Watch, my app no longer receives those background deliveries until the user opens the app again. What I would like to achieve is: When the app is terminated (swiped up), and there are new step count updates in HealthKit,
Topic:
App & System Services
SubTopic:
Health & Fitness
Tags:
Health and Fitness
HealthKit
Background Tasks
As explained in iOS Background Execution Limits ==> When the user ‘force quits’ an app by swiping up in the multitasking UI, iOS interprets that to mean that the user doesn’t want the app running at all. So: If the app is running, iOS terminates it. iOS also sets a flag that prevents the app from being launched in the background. That flag gets cleared when the user next launches the app manually. This gesture is a clear statement of user intent; there’s no documented way for your app to override the user’s choice. So, the best approach to this is first train your users so they understand that force quit will stop data collection. And if they still do it, then it is their choice for you to respect. So, how you solve this depends on your use case and the user experience you are trying to achieve. You can send push notifications if your server suspects that this has happened (no data updated for a while, for example) to encourage the users to tap on it, which will relaunch
Topic:
App & System Services
SubTopic:
Health & Fitness
Tags: