-
Notifications
You must be signed in to change notification settings - Fork 17
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
A crash in [[NSData alloc] initWithBase64EncodedString:response.payload options:0] when login #22
Comments
you can add this check before calling
|
Instead of checking error, the response should be check is it nil or not. Then only need to proceed further. Can you update this in code and share updated SDK. We are getting lot of crashes. if (response != nil) { |
Hi There, Hope you are doing great! First of all we highly apologies for the delay in response. The issue that you mention is resolved in the latest version of our IOS SDK. Therefore, I would request you to update the same Please feel free to write back via our support channel for a faster and dedicated response in case you face any confusion/issues, we will be happy to answer! -Parth |
There is a crash:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[_NSPlaceholderData initWithBase64EncodedString:options:]: nil string argument'
isAppWillTerminate-false
....
0x0000000105acdfb0 -[TCTrueSDK application:continueUserActivity:restorationHandler:] (in xxx) (TCTrueSDK.m:130)
....
The text was updated successfully, but these errors were encountered: