@DTS Engineer I think attachmentAnchor is not helping it just changes the position of the anchor on source view, I have attached weird behaviors between iOS17.5 & iOS18.0.
But in UIKit we can pass multiple arrow directions like [UIPopoverArrowDirection.up, .down] then based on the availability of the space system chooses the right arrow anchor but in SwiftUI it clips the content, please sample code below
struct Home: View {
@State private var showPopover: Bool = false
@State private var arrowDirection: ArrowDirection = .up
@State private var background: Color = .clear
@ViewBuilder
private var popoverContent: some View {
VStack {
Text("1240")
Text("124A")
Text("124A")
Text("124A")
Text("124A")
Text("124A")
Text("124A")
Text("124A")
Text("124Z")
}
}
var body: some View {
VStack(alignment: .center, spacing: 12) {
Text("Arrow Direction")
.font(.caption)
.foregroundColor(.gray)
Picker("", selection: $arrowDirection) {
ForEach(ArrowDirection.allCases, id: \.rawValue) { direction in
Text(direction.rawValue)
.tag(direction)
}
}
.pickerStyle(.segmented)
Text("Background")
.font(.caption)
.foregroundColor(.gray)
Picker("", selection: $background) {
Text("Default")
.tag(Color.clear)
Text("Blue")
.tag(Color.blue)
Text("Red")
.tag(Color.red)
Text("Orange")
.tag(Color.orange)
}
.pickerStyle(.segmented)
Spacer()
// Button {
// showPopover.toggle()
// } label: {
// Text("Show Popover")
// .padding(60)
// .border(Color.yellow)
// }
// .popover(
// isPresented: $showPopover,
// arrowEdge: arrowDirection.edge
// ) {
// popoverContent
// }
HStack {
Spacer()
Button {
showPopover.toggle()
} label: {
Image(systemName: "globe")
.font(.body)
}
.popover(
isPresented: $showPopover,
arrowEdge: arrowDirection.edge // change here
) {
popoverContent
}
}
//Spacer()
}
.frame(maxHeight: .infinity, alignment: .top)
.padding(15)
}
}
Post
Replies
Boosts
Views
Activity
I have two
FB13876192
FB13858544
Yes same issue for me, our deployment target is 15.0 already
I had talk with apple in their lab sessions and they admitted it's known issue in first beta and wait for next betas to have fix
This issue happening in Xcode16 beta1 when I run the app in iOS18 device
We are facing this issue in Xcode 15 beta 5
Same problem i filed feedback: FB12412988
I'm also facing same issue
@meaton
Thanks for reporting. I am assuming it is, but make sure that your embedded watchOS app is also signed during the iOS export process in Big Sur.
Yes during export process it's resigning watchapp but still it's missing -7 and -6 flags on bigsur i believe this must be Xcode issue will it resolve before final release of iOS15?
Just curios to know is there way to specify --generate-entitlement-der during exportArchive command else resigning app and extensions is like tedious process since we have many nested extensions internally?
@meaton
I'm still facing issue on watch app eventhough i'm on bigsur
after re-signing also it still shows CodeDirectory v=20400 so in which case this will change to 20500 ?
Also even i'm on bigsur so if i try to export archive and install it still fails so when i looked into pagesize flag -7 is missing, is it the expected issue even on bigsur after exporting archive?
ps: After export iOSApp.app seems to be contained 7, but extension like watchApp missing 7 but before export it seems to be fine any idea?
Same problem here
I have same issue sometimes in simulator as well, looks like to too many refresh it might be throttling
Oh this is so strange in terms of widgetkit i was battling with this from few weeks i ended by loading image in timeline provider, but i guess that would slow down rendering the widget, what interesting is that this sometimes work but sometimes not and not document anywhere i guess for aync image loading