Interactive Ink

MyScript SDK is working well in simultor but not in device - iOS

Dear Team,

Can you please help us with the solution to the crash getting in real device and not in simulator?

Also getting the below crashlog always when getting crashed:

"warning: could not execute support code to read Objective-C class data in the process. This may reduce the quality of type information available"


Thanks


Regards,

Smith


Dear Steve,


thank you for contacting us.


Which error message do you have? Can you confirm it is "Mismatch between certificate and application: com\.myscript\..+ != com.***", which I can see in your console?


If so, can you please check the 'bundleIdentifier' of your project?: https://developer-support.myscript.com/support/discussions/topics/16000007816.


If this doesn't help, can you please provide us with more information, so that we better understand the issue you are facing?


Best regards,


Olivier

Dear Olivier,


We are getting an "invalid certificate" error in older iPads like iPad Air 2, iPad Air etc.. (newer iPads are just working fine).

We already went LIVE with the recognition feature but this error is causing many problems for us.


Can you please help us with a solution?


Thanks,

Steve

Dear Steve,


It seems that you have reached your limit of licence consumption.

We have credited you with additional licenses and at the same time we found that the activated license counter increased.

Your problem should now be solved.


Let me know if you have any trouble about this.


Regards,


Maël

Dear Maël,

You're absolutely right. Thanks for the quick solution.


Thanks,

Steve

Dear Maël,

We are getting too many warning logs like below when we are processing the bulk points like below:

=============

[self.editor pointerEvents:pointerEvents count:eventCount doProcessGestures:NO error:&error];

[self.editor waitForIdle];

=============

Error Logs:

Swift.ImplicitlyUnwrappedOptional<Swift.String>.none

Swift.ImplicitlyUnwrappedOptional<Swift.String>.none

Swift.ImplicitlyUnwrappedOptional<Swift.String>.none

Swift.ImplicitlyUnwrappedOptional<Swift.String>.none

Swift.ImplicitlyUnwrappedOptional<Swift.String>.none

============= 

Can you please help us to fix this problem?


Thanks,

Steve

Dear Steve,


We tried to reproduce the issue with our Demo sample but we don't get such warnings.

Can you please provide us more details to understand and reproduce the issue ?


Regards,


Maël

Login or Signup to post a comment