“Xcode”

I am having the same issue on both of my machines (both running Xcode 26.4 and 26.4 simulators.) After setting the simulator back to iOS 26.2, I can work in the SwiftUI canvas.

Glad to hear you’re making progress. [quote='882117022, i12n, /thread/820580?answerId=882117022#882117022, /profile/i12n'] What's the documented behavior if the user has something actively playing on the system music player? [/quote] Sadly, I can’t help you with that. I waded into this thread because I have expertise in the entitlement side of things. Otherwise I’m a complete noob when it comes to MusicKit. I have a couple of recommendations: As I mentioned above, prototype stuff in Xcode, just to get your third-party tooling out of the mix. If you continue to have problems, start a new thread, using the same subtopic and tags as their thread (well, except for Entitlements). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='882177022, hbanzon, /thread/797959?answerId=882177022#882177022, /profile/hbanzon'] I just renewed my paid developer account today [/quote] This thread is about free provisioning, which Xcode displays as a Personal Team. The story for paid teams is different. My general advice is that you read through Developer Account Help > Devices. If that’s not sufficient, you can seek help via Apple > Developer > Contact Us. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881984022, Davidbaraff2, /thread/820572?answerId=881984022#881984022, /profile/Davidbaraff2'] There is a DHCP server on the local LAN to assign addresses to devices. [/quote] Do you actually need that? Or is this something you can’t control? [quote='881984022, Davidbaraff2, /thread/820572?answerId=881984022#881984022, /profile/Davidbaraff2'] if my iPad is trying to talk to anything on say 192.168 [/quote] Does that include multiple subnets? That is, does the DHCP server hand out a 192.168/16 address? Or does it hand out a 192.168.x/24 address? And in that case, are there resources on other 192.168.y/24 networks that you need to talk to? [quote='881984022, Davidbaraff2, /thread/820572?answerId=881984022#881984022, /profile/Davidbaraff2'] can you suggest any other way to accomplish this? [/quote] Depending on your answers to the above, you could potentially do this with an off-the-shelf VPN. Specifically, this would work if you can configure the VPN to: Always run over WWAN. Claim the default r

We see this issue in iOS 26.3 as well, but it can reproduce almost every time if we build the app with Xcode 26.4 and run the app on an iOS 26.3 device. Also sent: FB22305926 with the crash log.

These two statements are at odds: [quote='882101022, Arebus, /thread/820871?answerId=882101022#882101022, /profile/Arebus'] there is nothing special here [/quote] [quote='882101022, Arebus, /thread/820871?answerId=882101022#882101022, /profile/Arebus'] just a command line tool with a Localization.xcstrings file [/quote] Doing this is special because, in general, we don’t localise command-line tools on the Mac. Specifically, the traditional Unix-y way of localising command-line tools [1] is not standard practice on Apple platforms. Rather, Apple platforms use their own mechanism, based on the bundle structure. This mechanism is intended for GUI apps, and you have to jump through hoops to get it to work from the command line [2]. If you’re doing this just for testing, I recommend that you use Xcode’s testing infrastructure. It has options for overriding the language and region. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Roote

Thank you for your response, Richard. I have a follow-up question to clarify the exact trigger for the launch failure. Could you tell us which of the following scenarios actually causes the app to fail to launch? Built with Xcode 26 (iOS 26 SDK), run on an iOS 27 device — Does the app fail to launch simply because the device is running iOS 27, even though it was built with the older(=26) SDK? Built with Xcode 27 (iOS 27 SDK), run on any OS version including iOS 27 — Does the failure occur across all OS versions, including iOS 27(All OS versions(iOS15 or higher) supported by my app), as long as the app was compiled with the iOS 27 SDK without adopting the scene-based life cycle? Both of the above — Does the failure apply in either case? Understanding whether this is enforced at the OS level (runtime) or at the SDK/build level (compile time) is critical for planning our migration and release timeline. Thank you.

However, This UI glitch We have noticed not only on Toolbar but wherever we are using dropdown(Menu+Picker) throughout the app. It created different shapes while disappearing such as circle and capsule. In iOS 26.0 it shows capsule and iOS26.2.1 it shows circle like UI while disappearing. Is this existing issue in XCode/iOS26, If yes, When we can expect the fix from Apple?

Thanks for the update. Just to clarify: Starting from April we must use Xcode 26.X to upload apps to the App Store (using older Xcode versions will fail). In addition, Xcode 26.X deployment target is iOS 15+. So, no option to release apps targeted to older iOS versions? If this is the case, why this isn't blocked during the Xcode build process? or even during the App Store processing? Also, what about the apps we already published a week ago with target deployment 12.0?

Thank you for the reply, but according to the requirements on this link https://developer.apple.com/cn/app-store/submitting/, starting from April 2026, apps uploaded to App Store Connect must use iOS 26 SDK, which means Xcode 26 is also required. This seems contradictory to resolving the current issue. Could you provide the specific reason for the aforementioned problem? Why could the ipa compiled with Xcode 26 a week ago be installed, run, and used on an iPhone 6 12.5.8?

100% repro here. Xcode 26.4 is unusably slow and I am having to downgrade. FB22366086