-
Notifications
You must be signed in to change notification settings - Fork 111
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
LG-12920: add analytics event for tracking unexpected sdk error #10368
LG-12920: add analytics event for tracking unexpected sdk error #10368
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Acuant does not provide any information on what might trigger this. I think having this is better than not having it. We might want to add a note above the
window.AcuantJavascriptWebSdk.setUnexpectedErrorCallback((errorMessage) => {
like Unclear if/how this is called. Implemented just in case, but this is untested.
[skip changelog] Suggestion missed in #10368 that I think is a good addition.
[skip changelog] Suggestion missed in #10368 that I think is a good addition.
🎫 Ticket
LG-12920
🛠 Summary of changes
Implements the
setUnexpectedErrorCallback
method from Acuant setup instructions (step #5).We wanted to implement this now in case it gives us useful messages about the black screen issues in LG-12671.
📜 Testing Plan
I could not find a way to test this or to trigger it locally. It needs to be an error that happens after SDK load but before initialization. We would like to have a test for it, or at least have a way to trigger it manually, but we don't believe we have a way to do that.