Nah this still doesn't work for me. The back/forward list property implementation seems to be incorrect. Unceremoniously calling "load" inside the back/forward button handler doesn't make sense to me because there's no way for the WebPage to know that a back/forward action is taking place.

FB19034873

Is the back/forward list smart enough to know that calling ".load" with one of the URLs from he lists is enough to update the lists in the correct way?

@DTS Engineer Beta4 is not showing any improvement in this area. The back button, after going back to the first page, seems to still indicate there is still a back history, Is this code functioning correctly for you guys?

@DTS Engineer This example is fantastic, thank you so much. I am observing in beta 3, that the forward/back buttons do not dynamically enable / disable, despite my "WebPage" being added to my view as an @State. I figure this has something to do with a comment about "observability" (made in another thread about WebPage) not being ready yet.

Did you ever figure out how to navigate forward/backward using the BackForwardList? I’m absolutely stumped.

Could be nice to change up the UI to make it more glanceable or useful from a distance? Idk. Opens up options.

Sorry my title and body don’t make it clear. This is on Xcode Cloud. I can’t open a terminal to run the install command.

Is it possible to view an App's largest historical bundle version? I am encountering this problem now with a published app. Everything functions, it's just not visible to the user.

Please also file a feedback. We can not be solely responsible for making sure the frameworks function.

Please also file a bug ticket. We should not be solely responsible for Apple fixing their bugs.

So, I'm doing some exploratory coding with what is essentially a copy-paste of the code from the documentation. I am not seeing my OpenIntent show up in shortcuts as an action under my app, though. Currently my FileEntity.Query returns empty arrays because I'm not really intending on providing files from my application, just allow users to copy files into it.

Yeah, I caved and had to do something like the following: guard let collectionView, let item = item as? MODELTYPE, let index = dataSource?.indexPath(for: .url(item)), let cell = collectionView.cellForItem(at: index) else { return nil } return (cell as? CELLTYPE)?.imageView

thank you so much for jumping into this thread cause I'm here because of sequoia too

While this answer is not really satisfying, it fixed my problem. If you're applying a shader as a layerEffect to a SwiftUI view, make sure you declare a compositingGroup before the layer effect. This includes layerEffects that are wrapped in custom transitions. Otherwise the SwiftUILayer that gets passed to the shader acts real weird.