You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
On the Obj-C side, completion handlers are currently called immediately after the app event has been sent over the bridge. I haven't come up against any cases where this was disadvantageous, but I'm also not doing anything serious like fetching something over the network.
If this turns out the be a problem - an alternative implementation would be to store the obj-c completion handlers (no idea how to do this) by id, and pass that id over the bridge so that they can be invoked when the user calls done().
The text was updated successfully, but these errors were encountered:
On the Obj-C side, completion handlers are currently called immediately after the app event has been sent over the bridge. I haven't come up against any cases where this was disadvantageous, but I'm also not doing anything serious like fetching something over the network.
If this turns out the be a problem - an alternative implementation would be to store the obj-c completion handlers (no idea how to do this) by id, and pass that id over the bridge so that they can be invoked when the user calls
done()
.The text was updated successfully, but these errors were encountered: