Okay, I think I've isolated it more. My "hops like crazy" scenario was multiple LazyVGrids inside a single ScrollView. I'm going to assume that's not a supported configuration. I've attached a project and some videos to FB23182374 . Let me know if you have any questions or want me to try some things out on it.

Yeah. I'm at my wits end. I was hoping to unify some NSCollection and UICollection view code, but i don't think it's meant to be. Of course a sample project I made doesn't bounce near as much, making me even more confused.

Hmm, okay, that’s new. I’ve added the createAssets support and added Transferable to the PhotoEntity asset. I also think I finally got the photos app to try and invoke my add-to-album, though it says it failed and I still need to investigate. I have not been able to get siri to try to invoke my “add to album” intent with files from the Files app or tabs in safari. Should PhotoAsset AppEntity’s be cross compatible with other Entity types?

In this case it's not my photo! I'm trying to get an image provided from outside the app, so maybe an image from a safari web page. In that case my app's not on screen at the time. Does Siri have to bridge from Safari's provided AppEntity to my PhotoAsset entity? The PhotoAsset entity is very basic. I'll provide in a post

If I declare a Schema's AppIntent in my ShortCut provider, does that override siri's ability to do natural language processing for it? Maybe I'm just seeing early beta difficulties, but I've had no success getting siri to invoke intents that require inputs.

Please see my reply below about VoiceControl. It could help you out.

Does this still work? Running the code with this change does not appear to function in a way that makes the view focusable.

Is this on Xcode Cloud or Local? If local try installing the component from the Xcode Settings window. I've not had a problem build locally with the RC or during the past few betas.

It’s basically failing all the time for me now as well. I have some “green” builds in some older runs, but everything is red lately.

Yeah :. It sucks. Your best bet is to try to capture customer sentiment before they take steps to refund. Maybe soliciting reviews using the “review prompting” API that we have available. Could also add analytics to see if you can track user’s journeys through your app and see if there are obvious spots where you’re losing some, or frustrating others. It could just be that those users bought in and realized it didn’t solve the problem like they thought it would.

What information would be useful? The entire IPA? Other info from the bundle?

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?