Open tubibuto opened 3 weeks ago
Hello, thank you for reaching out! Could you please share the license number(starting LIC0..) with us so that we can inspect it and check its validity? You can find it in the developer hub portal.
Hello, thank you for reaching out! Could you please share the license number(starting LIC0..) with us so that we can inspect it and check its validity? You can find it in the developer hub portal.
@somyaguptagit It was trial license which did expire. I think the best course of action for this issue would be to actually reject promise if this part of the code responsible for license check fails. This way RN developer on JS side would be able to properly handle this new LICENSE_ERROR
type and prevent app from crashing.
What do you think?
Hello @tubibuto Thank you for your response! In order for our SDK to work properly, you need a valid license key so that you don't encounter any issues running it. However, we would kindly request you to contact us at support@microblink.com so that we can assist you further.
Hello @tubibuto Thank you for your response! In order for our SDK to work properly, you need a valid license key so that you don't encounter any issues running it. However, we would kindly request you to contact us at support@microblink.com so that we can assist you further.
@somyaguptagit I understand that and we updated the license with valid key, however we'd like to be able to have more control over unexpected errors coming form BlinkCard SDK side - for instance:
Currently if the license check code throws an exception, our app will crash since you don't reject promise in native code meaning we can't properly do error handling.
We have the issue where we can't properly catch the exception coming from native code in our Javascript code and it results in the App crash.