WildOrangutan

Ah, I see. I just wrote some random example, by using my imagination. So it probably only happens for querying then 🙂

I intend to use caching, so this exception is still relevant for me. Is composite exception there only because of cache-miss? What if you exposed some sort of callback for...

In case of "cache miss callback", I'd say network exception. But hm, in case of NetworkFirst this might get weird. `ApolloCompositeException` makes more sense when you take this into account....

From my pov, this would definitely better message what you can expect to handle. It would even better if we could somehow guarantee, that `suppressedApolloExceptions` won't contain `ApolloCompositeException` again :)....

> if there are 2, throw the 2nd one, but the 1st one is accessible through the standard suppressedExceptions (and clearly document that fact) Hm, I also like the idea....

@mrk-han attributes and measurement inspector don't really work with compose. Only one root `ViewGroup` is detected. It's not possible to inspect anything related to compose.