This bug has been fixed in Xcode 15.0 beta 2 (15A5161b).

Thanks a lot @malc for pointing out the release notes. I have also filed a feedback FB12335970 just in case it helps.

@Purkylin_glow @albert.tra Not sure if this is a good solution, but the following seems to work (it has downsides): List { ForEach(students.filter { $0.department?.id == department.id }) { student in Text(student.name) } } The downside is@Query would monitor changes and refresh the view even if a student is added to a totally different department. I really wish there is a better solution ...

@Purkylin_glow The problem with using department.students is that when the + button is tapped to add new students, it doesn't show up in the student list unless you go back to the department list and come back to Student list screen. New changes to department.students are not observed

@albert.tra Thanks, I have added @Relationship to var students in Department but doesn't work. I have pasted the complete code, you could also check at your end. I have tried it on Simulator for iPhone 14 Pro

@endecotp Thank you for the good suggestion and @Systems Engineer thanks for the confirmation. I was so confused if I was missing something obvious. @Systems Engineer so what is the IPSW file for (and how to use that)? I wish there was documentation about it, all I read was it is used by Apple Configurator but that is only for iOS IPSW files.

Not sure if the following helps, but that is what I did (after accidentally upgrading to macOS Sonoma). Xcode 15 beta will work on macOS Sonoma but you can't submit updates with Xcode beta. Note: I am no expert, so do with caution. How I wiped and installed macOS Ventura: Took a backup Downloaded macOS Ventura from the App Store Created a bootable USB disk of macOS Ventura Booted with USB, wiped disk Install macOS Ventura Copied files from backup. I still don't know how to download the macOS Sonoma installer without upgrading. Any help would be appreciated.

com.bluemangoo.tiennm642 Exactly, somehow Xcode is converting the P3 into sRGB in spite of explicitly specifying P3 assets and also the P3 assets have the correct metadata (color profile as P3 and color depth as 16 bits / channel) This seems like a bug in Xcode 14.3, it would be great if someone from Apple could verify this.

I am using the same computer display (Studio Display), when I open the icon image file in Preview color is correct, but when I see the underlying file in the IPA (inside the IPA) the color is wrong. Also when installed on the iPhone which supports Display P3 the color is wrong. I feel I am missing something obvious, because according to Xcode it seems to support Display P3. I even tried individual icons for Display P3 and sRGB. I used the same Display P3 icons in sRGB and Display P3 slots.

@Claude31 I am able to submit more than 2 per day, when I add external testers via App Store Connect Also interestingly Xcode Cloud build fails only for mac This definitely seems like a bug.

Please help the following is the password that XCTest was requesting on my Mac: This is required for the Mac, for iOS it runs without asking for password, So I am wondering if this is the reason why XCTest for the Mac doesn't run on Xcode Cloud. I found this post regarding the same https://developer.apple.com/forums/thread/693850 Question: I am not sure how to run automationmodetool disable-automationmode-without-authentication on Xcode Cloud?

Yes I just noticed this issue, it seems like sometimes the query results are cached. What worked for me: Query some other entity and get the results Then go back to your interested entity and query again (hopefully you should see the record changes)

@Developer Tools Engineer Yes the app successfully compiles and runs on both platforms. Questions: What is the password entry requirement during local test? Based on the error message /Volumes/workspace/resultbundle.xcresult on Xcode Cloud? I couldn't find it, there is very little I can do. If I provide app name would it be possible for you to investigate? Is there any way to resolve / understand the issue? Note: I remember when I first pressed Command U (Product > Test), the app did ask for some authentication and I had press the Touch ID / enter macOS user password for it to run. The app doesn't do any authentication on it is own. Scheme: I had deleted a target and added a target so I ended up adding my scheme and I had to add the Tests (UI and non-UI) in the scheme.

Thanks Claude31 for the clarification. External testing vs Internal Testing I suppose there can be any number of internal builds in a day, however only 2 builds can be submitted for review for External testers Errror Xcode Cloud is integrated into Xcode and reports status from AppStoreConnect, IMHO this seems more like a bug where this particular scenario has not been handled. Even AppStoreConnect doesn't actually show the error unless I try to add external testers. The fact that Xcode Cloud attempted to add external testers should have triggered the error in AppStoreConnect but however it doesn't seem to have or at least doesn't display in AppStoreConnect. After that it should be relayed to Xcode I hope the Apple Engineers could have a look at this. Thanks.

@Iomegan For the Mac the issue still exists, iOS works. I have filed a feedback. In case you want to use it on the Mac you could NSItemProvider API, these APIs are older and in my humble opinion that in the future Transferable APIs would gain more capabilities