i think this approach works, but i don't really like it.

that said, i also don't have a better idea off the top of my head.

@emdobrin and @praveek would you mind thinking about alternative ways to solve this?

Apologies for the delay. I missed the GH notification.

Another way to simplify the logic is to avoid using MobileCore.dispatchWithResponseCallback in the public API layer. Since Core handles the timeout, Optimize should be aware of the timeout when making the API call.

Instead

1. Optimize extension can dispatch a chained event (not one time response event) that the public API layer listens for and handles the callback itself.
2. Follow how Edge manages the completion handler. While this bypasses the event hub, it makes the API layer cleaner and ensures a more consistent behaviour.