The SHRINE query entry point received a response from the hub that was not the expected AggregatedRunQueryResponse .

Since 1.23


The hub has responded to the query entry point's request to run a query with something other than the expected AggregatedRunQueryResponse. However, more primitive code in the query entry point was able to interpret the response as some other SHRINE response. The query entry point does not have logic to proceed.


Please report the summary, description, and all details to so that we can investigate and fix this bug. 

Retired in Shrine 2.1

  • No labels