@userkv No. Pleas file a feedback if convenient 🙏
Gong
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
Post
Replies
Boosts
Views
Activity
@interferon Some of the objc libraries failed to link due to this issue. 🥲 Not solved yet.
Up vote for iCloud auth support in vm. Again. 😂
Reading other people's code can be very helpful, especially for real-world projects. Recommended:
https://github.com/skjiisa/Tickmate-iOS
Reported FB12531495
Got same warnings in Xcode 15 beta 3. But beta 2 and 1 are good....
Related issue: Unable to set initial/default window size
WindowGroup {
ContentView()
.frame(width: 300, height: 400) // imperfect, the ornaments still layout as the original size
}
.windowStyle(.plain)
.defaultSize(width: 1.5, height: 2, depth: 0, in: .meters) // no effect on plain window
Reported: FB12507146
Same here. See only one intent suggestion on the entire iOS 16 year...
@Developer Tools Engineer 😄 Thank you for the response! I didn't expect you to pay attention to this minor interface error. I have already submitted the feedback (FB12404233). Thank you once again!
@simonfromhelix Thank you very much! I did indeed migrate to a Single Target Watch App in the update to watchOS 9 last year. The changes to the bundle Identifier and the issue with system caches seem to explain this issue well.
Thanks again for providing this helpful information. This community is really great!
Still crash on iOS 16.3 + Xcode 14.2
@ViewBuilder
func complicationLayer(_ layer: Compatibility.ComplicationLayer) -> some View {
if #available(watchOS 9.2, *) {
switch layer {
case .foreground:
self
case .background:
self.complicationForeground()
}
} else {
switch layer {
case .foreground:
self.complicationForeground()
case .background:
self
}
}
}
It's ugly but it works. I don't want Apple to reverse its semantics again, even if it's wrong. So be it.
This issue can only be reproduced on the physical watch with watchOS 9.2 at this time. There is currently no simulator available for watchOS 9.2 in Xcode 14.2. Also, It is worth mentioning that the SwiftUI Preview also does not correctly render the replicationForeground() effect. But this should be another bug.