After updating to xcode 26 beta 4 + ios 26 beta latest, I could no longer repro the reported issue because the entire Visual Intelligence framework stopped working for me, without code changes. Things that were working before, such as IntentValueQuery is no longer executed. And I'm seeing new errors as below: nw_read_request_report [C5] Receive failed with error "Operation timed out" nw_endpoint_flow_fillout_data_transfer_snapshot copy_info() returned NULL nw_read_request_report [C23] Receive failed with error "Operation timed out" nw_endpoint_flow_fillout_data_transfer_snapshot copy_info() returned NULL Failed to terminate process: Error Domain=com.apple.extensionKit.errorDomain Code=18 "(null)" UserInfo={NSUnderlyingError=0x10c9e1b60 {Error Domain=RBSRequestErrorDomain Code=3 "No such process found" UserInfo={NSLocalizedFailureReason=No such process found}}}

Thank you for the very detailed response! I'm still a bit confused about the usage of IntentValueQuery and EntityQuery. It seems normally AppEntity is only mapped to EntityQuery, but in Visual Search Intelligence framework, IntentValueQuery is added to provide search results based on a given image. You mentioned that when object is tapped, it gets the id from AppEntity object, use it to search in EntityQuery.entities(for:), and get an AppEtity back, it seems to be a redundant step if we already had the AppEntity object in the beginning? Additionally, search results provided in IntentValueQuery come from network call. If we want to be able to search within these results in EntityQuery, does it mean we'll have to store a copy of these objects somewhere? It seems unsafe to do so, and there isn't a proper chance to remove them from storage when no longer needed. Not sure if I missed anything from the Visual Intelligence framework, but looking forward to your answers!

I also updated the testing project based on your advice: implementing EntityQuery.values(for:) does enable the OpenIntent Looks like I can cheat EntityQuery.values(for:) by creating a new Entity with same id, which seems to add unnecessary risk. But returning the correct Recipe Entity instance relies on keeping a copy of RecipeEntityInventory which seems ideal for a real world case where the results come from network work.

I understand how it work now, thank you for your explanation! Sounds like usage of EntityQuery is required by the Intent framework, and Entity for Visual Intelligence is not exempted from it. I understand it allows AppEntity to be more verastile, although personally I think the Entity->ID->Entity retrieval process could be optimized in the case of Visual Intelligence, assuming there's an underlying collectionView that maps each cell to the Entity instance. Thanks again for your help!