Same, and solved with the non-App Store version. Both show build as 12A7209, but the App Store version shows a Created date of Aug 25 vs Sept 9.
CALL-151
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Louisville, KY, United States
Post
Replies
Boosts
Views
Activity
The developer documentation issue is limited to the App Store version of Xcode. Download directly from https://developer.apple.com/download/more/ to regain access to documentation. This does not solve the Spotlight crash.
This is limited to the App Store version. Download Xcode from https://developer.apple.com/download/more/ to regain access to the developer documentation.
The solution posted by TripleMonkey worked for me. No need to delete derived data or change the GPU selection. Thanks!
The simplest solution to issue #1 is to place your views (10 or less) into Groups, e.g.:
Group {
Text("Hello, World! 1 ")
Text("Hello, World! 2 ")
Text("Hello, World! 3 ")
Text("Hello, World! 4 ")
Text("Hello, World! 5 ")
Text("Hello, World! 6 ")
Text("Hello, World! 7 ")
Text("Hello, World! 8 ")
Text("Hello, World! 9 ")
Text("Hello, World! 10 ")
}
Group {
Text("Hello World! 11 ")
...
}
Reply to
SwiftUI TabView with PageTabViewStyle calls onAppear of children multiple times on iOS 14.2
This situation has gotten even worse in iOS 14.3. The only reliable solution I've found is to abandon .onAppear/.onDisappear, use a @State var to track TabView transitions with .onChange, AND debounce calls to .onChange which can occur one or more times. See:
[https://stackoverflow.com/questions/64641759/swiftui-pagetabview-in-ios14-2-will-recall-childview-onappear-method-many-times/65542867#65542867)]
Still not working in the U.S. Sigh...
Watch https://developer.apple.com/system-status/ for resolution.
Still unable. visionOS 1.0 Simulator is installed as a platform, but I can't select it as a run destination or add it to a target as a supported destination.