-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Race Condition #2
Comments
The Alternate Implementation described in this workaround seems to workand solves this issue for now. A more permanent solution is slated for the next release in late Q1/ beginning of Q2. |
Fhttp://www.javadoc.io/doc/com.braintreepayments.api/braintreehttp://www.javadoc.io/doc/com.braintreepahttp://www.javadoc.io/doc/com.braintreepayments.api/braintreeyments.api/braintree |
Thttp://www.javadoc.io/doc/com.braintreepayments.api/braintree |
In version 3.1 of the Kount Android SDK there is a race condition that results in data not being collected. If you call
DataCollector#setContext
right before (usually in the same event loop) callingDataCollector#collectForSession
the failure callback is always called withDataCollector.Error.CONTEXT_NOT_SET
the first time or whenever theDataCollector
singleton is not in memory.This is a result of the
WebView
being creating inside of aHandler
on the main thread,DataCollector#collectForSession
will execute before theWebView
has been created and the check for theWebView
will fail and result in the failure callback. Since responses are already communicated back via callbacks it would be nice to wrap the code and check inside ofDataCollector#collectForSession
inside of aHandler
or similarly alter the check to avoid this race condition.
Thanks!
The text was updated successfully, but these errors were encountered: