Xcode

Thank you for sharing your post. Have you attempted using the latest Xcode beta? What version of Xcode are you using? The warnings you are receiving indicate that Auto Layout is attempting to resolve conflicting constraints. Since you have not explicitly used Auto Layout in your code previously, it is likely that Auto Layout is relying on implicit constraints generated from the frames and autoresizing masks of your views. When you create views programmatically and do not intend to set constraints manually, such as in the following example: toolbar.translatesAutoresizingMaskIntoConstraints = false

 https://developer.apple.com/documentation/uikit/uiview/translatesautoresizingmaskintoconstraints If your toolbar is embedded in or interactIn contrast to other views, ensure that those views also have the translatesAutoresizingMaskIntoConstraints property set to false and appropriate constraints added. By adopting explicit Auto Layout usage, you will not only eliminate these warnings but also gain

Hello. We have not received a bug report number from you so I cm unable to check on status. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

Using Xcode 26.2, targeting an iPhone 17 Pro running 26.1, Xcode crashes saying the symbol isn't available. The isEligibleForAgeFeatures property is actually available in iOS 26.2 beta or later. The documentation showing it as iOS 26 is a bug. Thank you for filing your Feedback report. Upgrade your device to iOS 26.2 beta to test it.

Thanks for the post and the animation that worked for 12 years. What Xcode are you using? 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. This will help so I can see and test on my environment to see if something has changed and now is causing an issue. Albert Pascual
  Worldwide Developer Relations.

I have exactly the same issue on XCode/iOS 26.1. Did you find more info on this issue ? I'm surprised it's not reported by more people

Not relevant. In App Store Connect settings -> Edit Profile -> Xcode Cloud -> the old account was displayed, after deleting and replacing it everything works

[quote='866998022, imaier, /thread/807154?answerId=866998022#866998022, /profile/imaier'] Does it need the is-Beta-App flag? [/quote] No. My expectation is that this wouldn’t be set. And yes, that flag is primarily associated with TestFlight. [quote='866998022, imaier, /thread/807154?answerId=866998022#866998022, /profile/imaier'] The code signing info from launchctl procinfo looks exactly like yours [/quote] Interesting. If, yesterday, you’d made me guess as to this result, I would’ve guessed the opposition. This results rules out my main theory as to what’s going on, namely that your app group was causing your entitlements to get invalidated. This is something I talk about in the Entitlements-Validated Flag section of App Groups: macOS vs iOS: Working Towards Harmony. And that leaves me out of ideas. My best guess right now is that this problem is the result of the different install machinery used on iOS and macOS. Well, the lack of install machinery on macOS, where Xcode just constructs the app an

Same error. XCODE Version 26.0 (17A324) Apple Watch Series 8 watchOS 26.1