Any update almet ? Cihadturhan? Did your app finally approved or reject?

Thanks ! Changing my Inner VStack to a LazyInnerVStack fix the issue!

not for me :(

Did you finally solve it?

Thanks @robnotyou! This page tell that iPhone 14 Pro should be Screen resolution (points): 393 x 852 and Native resolution (pixels): 1179 x 2556 (460 ppi) That is coherent with simulator but not with real device logs...

Thanks for your feedback. No, no mix-up. Real iPhone 14 Pro of one of my user reports 390x844 @3x = 1170x2532. Unless iPhone15,2 is not "iPhone 14 Pro" it seems that with iOS 16.0.2 iPhone 14 Pro is exposed with same screen size than iPhone 12, 13, 14, and 12 Pro, 13 Pro. Here is the custom log I'm receiving from my user device : iOS Version: iOS 16.0.2 / ModelName: (iPhone15,2) / ScreenBound: 390.0 x 844.0 / NativeScreenSize: 1170.0 x 2532.0 / ScreenSize: 390.0 x 844.0

Thank you very much ! Would you mind having a look to that question too: https://developer.apple.com/forums/thread/733102?login=true&page=1#761114022 I having hard time to work around that issue with Widget Interactivity that sometimes (when tapping multiple times on a widget button) opens the app ignoring the tapped button intent. I Just need to know if this is considered as a bug that will be fixed before iOS 17 release or if interactive widgets are not supposed to be fully interactive.

Usage of @Environment(.showsWidgetContainerBackground) seems to cause a crash on iOS 17 beta 6 when compile with Xcode 15 beta 6. Symbol not found: _$s7SwiftUI17EnvironmentValuesV9WidgetKitE05showsE19ContainerBackgroundSbvg My only solution was to stop using that environment var for the moment...

Thanks for information. I'll need to support iOS version before 17.4 so I will use two containers (one per conf) but can I use both at same time or should I switch ? In the example below, still only first container is loaded... var firstContainer: ModelContainer var secondContainer: ModelContainer var body: some Scene { WindowGroup { HomeView() } .modelContainer(firstDataContainer) .modelContainer(secondDataContainer) }

Updating your Google Mobile Ads SDK to 11.2.0+ (and if necessary UMP SDK to 2.3.0+) could also help.