I was seeing this issue earlier, but now the behavior has changed, and clicking the "Invite" link just spins forever in the browser. I've tried in multiple browsers (Chrome and Safari), have tried Incognito mode, have tried both signed in and not signed into the Apple ID, and have tried deleting the user and re-submitting the Invite link (multiple times). No matter what I do, the link spins forever and the user can not accept the invite.

Thanks for the detailed response! To answer your questions: OAuth - I don't see a pattern other than time. It seems to lose the OAuth token 2 or 3 times per day. It also doesn't seem to depend on idle time. I can be in the middle of working and it will lose the token. Yes, especially since thinking can go off the rails or go into a nearly-endless loop, this serves as a way to monitor and guide agent progress. I did file a feedback on all the issues, btw! (FB22310171 on the whole set of issues, and I also just filed FB22316631 per your request on this specific one.) Next time this occurs, I will attach it to the Feedback report. No, I have never downloaded or setup Codex. I especially want to highlight the additional bug I reported in my Feedback report but did not post here -- the agent will take action even if I specifically tell it to ask for approval before proceding. This is concerning because there is now some internal state where the agent believes it has gotten permission even though it hasn't. (It literally says this in its thinking bubble.) Thanks!

One more issue: I'm seeing Claude Agent just randomly stop in the middle of working. After submitting a prompt, it will occasionally respond with "Let me start by understanding the current (whatever) implementation." And then do nothing. This is different than the OAuth issue, as the OAuth token is still valid in this case.

Same here. I'm seeing this, and other Coding Intelligence regressions.

Following up -- I filed a Feedback on this, and it was marked as: "Resolution: Investigation complete - Works as currently designed" What am I missing here? This really does not seem like intentional behavior.

This continues to fail for me on Xcode 15 beta 4 on the iOS 17 simulator. Same authentication error to the WeatherService.

This issue still exists for me in Xcode 15 Beta 3. I am very surprised that this hasn't been addressed yet, or even mentioned in the Release Notes. Based on the discussion in this thread, no apps using WeatherKit can be built or run on iOS 17 yet. Has anyone been successful in getting WeatherKit to work on iOS 17?

This is still a problem for me on Xcode 15 beta 2. I inspected the built .app using codesign: codesign --display --entitlements :- YourApp.app And it is in fact missing the com.apple.developer.weatherkit entitlement, despite the fact that it is included in the project's Entitlements file.

I'm also seeing the same issue with WeatherKit on iOS 17 / Xcode 15 beta 1. I noticed that others are experiencing more general issues with entitlements apparently not working in Xcode 15 B1, even when configured correctly: https://developer.apple.com/forums/thread/731010 https://developer.apple.com/forums/thread/731116 I'm wondering if the WeatherKit issue we are seeing is a specific instance of this issue -- in this case, the com.apple.developer.weatherkit entitlement not getting picked up correctly. I could imagine this potentially causing auth issues on the backend. Speculation at this point, but it seems to fit.