Change section.orthogonalScrollingBehavior to continuous or other behavior, It can cause this problem, I have report this bug to apple in feedback, but there is no response yet. let section = NSCollectionLayoutSection(group: group) section.orthogonalScrollingBehavior = .continuous

In my case， when I update to xcode13 and iOS15。 I have found that navigationBar and tabBar turns transparent。 My viewController is embed in UINavigationController After a series of tests, I found the Settings the backgroundColor of navigationController is best Way to fix this navigationController?.view.backgroundColor = .yourColor Once the color is set, everything is fine

In my case, I found Xcode source control caused the problem To fix this problem Xcode -> Preferences -> Source Control uncheck Enable Source control. Then restart Xcode, everything will be fine

same issue, watchOS 8.3

I have the same issue. After the test， I found out that the problem was I move storeURL to shared container(App group), and then fetch CoreData in widget extension In most time, the app works fine. But when I change dataModel, The problem arises。 In Debug, when I run project, CoreData migrate store automatically and there is no problem, because I'm not running widget extension at this point. In Production, when I update app from an old version, CoreDataStack container loadPersistentStores failed some time. I think both app and extension fetch sqlite file at same time case migrate failed When I remove the code from the widget that accesses coreData, the problem goes away I hope I can help others who are going through the same problem as me

It is recommended to use WidgetBundle instead of creating multiple extensions. In Xcode14, I create two extensions, one of them will not be displayed. Use WidgetBundle All the problems go away

same issue, do you find solution?

I also encountered the same issue. No matter which sandbox user I logged in with in the settings, the app downloaded from TestFlight always used my App Store Apple ID instead of the corresponding sandbox user. My solution is: Log out of the sandbox user in settings. Download the app using TestFlight. Log out of the Apple ID logged in through the App Store (this is the most crucial step). Open the app and proceed to make an in-app purchase; at this point, the app will prompt you to log in. Use your sandbox user account to log in. This method allows you to test in-app purchases with the sandbox user. I hope Apple can fix this issue soon.

I encountered the same issue. I have an ARKit app, which in Xcode 14 could directly load the .rcproject created with Reality Composer into the project. However, after upgrading to Xcode 15, this project can no longer be previewed or adjusted. The current tool is Reality Composer Pro, which apparently does not support .rcproject and .reality files. Therefore, we first need to use Reality Composer in Xcode 14 to export to USDZ. For the exporting method, refer to this link: https://developer.apple.com/documentation/realitykit/exporting-a-reality-composer-scene-to-usdz Then, we need to adjust the app to load and use the USDZ file instead of loading the reality file's URL. This way, any subsequent updates will only require adjusting the USDZ file, which currently seems to be a better approach.

same issue