Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

NativeApi.InitializeAsync() not really async

See original GitHub issue

Currently NativeApi.InitializeAsync() wraps NativeSdkMethods.Init() to return a Task. However, NativeSdkMethods.Init() does take a while to start (about 300ms on my laptop), blocking the calling thread.

I’d suggest to spin a new thread doing something like this:

return Task.Run(_nativeSdkMethods.Init)
   .ContinueWith(/* error handling */);

Thoughts?

Issue Analytics

State:
Created 4 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

Sharparamcommented, Feb 28, 2021

Latest docs in release branch now have a note in the getting started guide about needing to wait for a couple seconds or use the method of listening for the DeviceAccess event.

0reactions

Sharparamcommented, Jan 31, 2021

I’d rather document this clearly so users know what to expect.

Hm, that might be the way to go. Document it and then users can either use the event loop if they have it available (optimal), or insert an artificial delay of a second or two that should leave enough time to init (not as accurate, but probably good enough if it’s not feasible to get the event loop).