The following workaround seems to have worked for me - I noticed that my icon image files were created in different color spaces. The light and the dark files were in RGB whereas the tint version was Gray. And for some reason, App Store Connect was pulling the tint version. So I recreated the tint version. I changed the colors of the elements to grayscale (in the authoring tool), but saved the file in RGB color space. Then re-submitted the binary with the updated icon files to App Store Connect and it seems to have worked. App Store is now extracting the light version from all these apps. Hope that helps.

The following workaround seems to have worked for me - I noticed that my icon image files were created in different color spaces. The light and the dark files were in RGB whereas the tint version was Gray. And for some reason, App Store Connect was pulling the tint version. So I recreated the tint version. I changed the colors of the elements to grayscale (in the authoring tool), but saved the file in RGB color space. Then re-submitted the binary with the updated icon files to App Store Connect and it seems to have worked. App Store is now extracting the light version from all these apps. Hope that helps.

I encountered the same error and stumbled onto this thread. Its helped me fix the issue, using another solution - in case anyone is interested. My List displays search results based on two search parameters, and the results were clubbed into Sections, where each Section consolidated the results for one parameter. The List displays fine when the search is first run. But changing the parameters or the interval caused the Sections to change their order leading to the same crash as described on this thread. I solved it by assigning an ID value to the List. And then changed this ID each time the user taps the search button to generate a new search. eg @State var listID = 1 List { ForEach(parameter1){ Section { //all the rows matching this parameter } } } .id(listID) //this solved the issue Button(action:{ self.fetchResults self.listID += 1 //increment the ID, thereby causing the List to reset its state and prevents the crash }, label: { Text("Search") } ) Hope it helps anyone who faces the same crash error!

I'm facing the same issue. Followed the instructions and code samples as shown in the documentation but the problem still persists. Any updates on the solution to this?

Facing the same issue. This was NOT happening in Beta 3. I experienced this issue only after upgrading to Beta 5. Also, the crash happens only AFTER the GKAccessPoint is made visible once. i.e. after GKAccessPoint.shared.isActive is set to true, and then later set to false. Setting it to false all throughout, without making it visible even once, doesnt cause any crash.