Posts

Post not yet marked as solved
8 Replies
Same issue. Have you filed a Feedback Report? Here's mine: FB13455112
Post marked as solved
2 Replies
I'm seeing similar behavior even when using @State variables, although it appears to be inconsistent. Sometimes it shows the view without issue, other times it spits out the console warning "Attempt to present which is already presenting <TipKit.TipUIPopoverViewController>
Post not yet marked as solved
1 Replies
Did you ever get this sorted?
Post not yet marked as solved
1 Replies
I see these errors after a successful initial share. I can share one record just fine. Any subsequent shares of other records produces these same messages.
Post marked as solved
5 Replies
Would also like to know if this is an option yet!
Post not yet marked as solved
54 Replies
@TheXs2490 How would this work if View1 looked like this: struct View1: View{ var body: some View{ LazyVGrid(columns: gridLayout, spacing: 10) { ForEach(Array(person.item! as! Set<Item>).sorted { $0.date! > $1.date! }, id: \.self) { (item: Item) in NavigationLink(destination: View2(){ Text("Navigate") } } } } } I can't get it to compile properly if the if self.KeepView2 is right before the NavigationLink. And if I put it before the LazyVGrid, it won't display the contents of the ForEach Array. Thanks!
Post marked as solved
20 Replies
Hi all - has anyone seen an actual fix for this issue? iPadOS 14.7 still exhibits this behavior in my apps. The multiple NavigationLinks in a single view appear to work on my iPhone app, but break on iPad and Mac Catalyst. The EmptyView() workaround doesn't work for me. And I'm not interested in rewriting my entire navigation over this. I've filed a bug, but haven't heard anything back from Apple. Has anyone heard back from the bugs they've filed? This is super frustrating!
Post marked as solved
36 Replies
Found this thread after having issues with my widgets in TestFlight as well. Is the solution in this thread also required for publishing to the App Store? Our only for test flight?
Post not yet marked as solved
2 Replies
Have you had any luck with this one?
Post not yet marked as solved
2 Replies