It appears that there’s currently no way to delete a game from the Games App Library. However, you can click the filter button and select only installed games instead of all the games you’ve played on your iPhone. If you’re looking for a more comprehensive feature, you can always submit a suggestion through the Feedback Assistant application.

Beta software is notorious for unusual battery drain; I have experienced this on my iPhone with the iOS 26 beta installed. The new Liquid Glass design could be using much more battery than the previous design because of the complex shaders and graphics effects. Or, this could simply just be a bug in watchOS 26. If possible, I would recommend attempting to restore your Apple Watch to watchOS 11 unless it is absolutely necessary for development purposes.

I would recommend reporting this bug to Apple in the Feedback Assistant App (it should appear on any device running Apple beta software). If necessary, you can reset your iPad to iOS 18 using iCloud backups (if you have any). This will likely be ironed out in a future developer beta. I hope that this helps!

I rebuilt the project in Xcode 26.0 beta 2 using the iOS 26 beta 2 SDK and the issue persists. I tried to create a test project. However, I was not able to keep it within reasonable size and not include my entire codebase to reproduce the issue. Therefore, I am not quite sure what is causing this "circular reference issue" because, at surface level, there doesn't seem to be a circular reference of any kind in my data structures. Could this be a bug with the beta Xcode or SDKs as this is not an issue in Xcode 16? Have there been any changes from iOS 18->26 or Xcode 16-> 26 that change the Swift Compiler regarding circular references?

Adding nonisolated to my struct fixed the issue. My project is, as well, on MainActor default isolation mode. Although this fixes the problem, I am not sure about any repercussions that this might have in terms of concurrency. I am also new to Swift concurrency (I found Embracing Swift Concurrency from WWDC25 to be very helpful if you haven't watched it already). However, I am not sure if this is intended functionality or not because the error gives very little information. Thanks for your solutions!

Please submit a bug report in the Feedback Assistant app as that is the quickest way to let Apple know about your issue. Best of luck!

After my first time building my code in Xcode 26, I got the first error that you mentioned. So, because I was not using the Encodable part of the Codable conformance, I simply switched it to Decodable and it made that error go away but kept the circular reference bug. Then, I followed KeithB's solution and added nonisolated to each struct that was throwing that error. I am new to Swift Concurrency and don't really know what repercussions this change could have on my codebase and concurrency (I assumed that it wouldn't be critical because of Swift's data race safety). I am using these structs as a way to decode JSON into a struct from an HTTP GET/POST API. I am sending a request to the web service and receive the JSON in exchange. I use the built-in JSONDecoder to decode. All of the JSON processing runs in an asynchronous function so that it doesn't cause any hangs in my app. As of right now, with KeithB's solution, my app is working fine but as I potentially integrate more concurrency later in development, will there be any issues directly stemming from using nonisolated as opposed to MainActor?

I would assume that that is fine. I think that as long as the JSON data received from the GET request contains no personal information, you're fine. Additionally, as far as I can tell from your original post, you are not sending any POST requests that are giving app data to the server. If you are, this might be a different question. Also, I would think that the phrasing "we do not collect data from this app" referes more to analytics that user settings and preferences.

I would recommend submitting a bug report in Feedback Assistant so that your issue gets directed to the Apple engineers.

From my understanding, Apple Intelligence is not available on iOS simulators in Xcode: that is why you must run the code on your own Mac for it to work. Have you tried running this code without the #Playground macro? I don't think that that would make a difference but it would be good to rule it out. However, the code should work the same on iOS and macOS. If you must test your code on an iOS device, you could try it on your iPhone with the iOS 26 beta installed (assuming that your phone supports Apple Intelligence).

I am experienced this issue on the Tahoe public beta as well and it is very frustrating. It also happened to me while just writing code (maybe because the preview canvas was updating while I was writing my UI code).

Thank you! I have filed a bug report for this. The bug number is FB19284368.