I am a new developer but here is my issue...I am experiencing a persistent WeatherKit authentication failure in my iOS app, resulting in the error WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2. I have verified my configuration and am looking for guidance on next steps. Environment: Xcode Version: 26.6 iOS Version: 26.6 Device: Physical iPhone Apple Developer Program: Paid WeatherKit Usage: Native WeatherKit.WeatherService API (not REST) Steps Already Verified: Xcode: The WeatherKit capability is enabled in Signing & Capabilities. Apple Developer Portal: The WeatherKit capability is enabled for the specific App ID (com.carmineloschiavo.X-StreamWeather) under App Services. Entitlements: The com.apple.developer.weatherkit entitlement is present in the signed app binary and the embedded provisioning profile. Bundle ID: The Bundle ID in Xcode exactly matches the App ID in the portal. Provisioning Profile: I have regenerated the provisioning profile after enabling WeatherKit. Clean Environment: I have performed Clean Build Folder, deleted the app from the device, and restarted the iPhone and Xcode. Waiting Period: I have waited over 24 hours after enabling WeatherKit. The issue persists with the same error. Additional Diagnostics: The error occurs during JWT generation before any weather data is returned. The device-side auth log shows [AuthService] Signed successfully but then Failed to generate jwt token ... Code=2 . The error is consistent and prevents any WeatherKit data from loading.

I am trying to create a new app using IOS-26.1, macOS Tahoe 26.1 and Xcode 26.1 with Swift6. Is this a bug that is going to be addressed. This is in the Debug Console...Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "<NSAutoresizingMaskLayoutConstraint:0x10bb18870 h=--& v=--& _TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0.width == 0 (active)>", "<NSLayoutConstraint:0x115ac2ee0 _TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0.leading == _UIButtonBarButton:0x115d40c80.leading (active)>", "<NSLayoutConstraint:0x115ac30c0 H:[_UIButtonBarButton:0x115d40c80]-(0)-| (active, names: '|':_TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0 )>", "<NSLayoutConstraint:0x115ac2df0 'TB_Leading_Leading' H:|-(12)-[_UIModernBarButton:0x115d20a80] (active, names: '|':_UIButtonBarButton:0x115d40c80 )>", "<NSLayoutConstraint:0x115ac2fd0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x115d20a80]-(12)-| (active, names: '|':_UIButtonBarButton:0x115d40c80 )>" ) Will attempt to recover by breaking constraint <NSLayoutConstraint:0x115ac2fd0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x115d20a80]-(12)-| (active, names: '|':_UIButtonBarButton:0x115d40c80 )> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.

Can anyone help me rename my project safely using 16.2. I looked around but only found help for earlier versions?

What is the safest way to rename a project so the app still works using Xcode 14.2. I’ve seen instructions using earlier versions of Xcode but with the latest version it’s a bit confusing.