authToken is empty

  • Last Post 01 July 2013
meera j pai posted this 20 June 2013

I was just trying out a sample project on OCR. I got it from gitHub link. I added the applicationId and password and when I execute it, it gets crashed as the token is empty. This is the point where its crashing.

NSString *installationId = [responseDictionary valueForKey:@"authToken"];

[[NSUserDefaults standardUserDefaults] setObject:installationId forKey:kOCRSDKInstallationId]; NSParameterAssert(self.installationId);

I cant figure out what I am doing wrong here. Please help

Order By: Standard | Newest | Votes
meera j pai posted this 24 June 2013

What could be the reason for this? Should i have to be a paid user to be authenticated?? I just wanted to have a free trial first. Thanks in advance....

meera j pai posted this 24 June 2013

According to this question in ABBYY Forum there is another hex value for applicationId which doesn't come in the email from ABBYY on registering the app. Its visible in the HTML content of the website. And on replacing this I don't get the crash instead I get 401 error. Now i don't get whats wrong here? Any guess why its happening so?? Thanks in advance.

Anastasia Galimova posted this 28 June 2013

Dear Meera,

We apologize for the long delay.

1) According to the logs of your account, you have registered two applications: "OCRTestDemo" and "CharacterReaderDemo". Only the first one has available pages for the recognition for free. Could you please clarify, if the error occurs when ApplicationID="OCRTestDemo"?

2) As I see from your post on Stackoverflow, you use iOS. Have you followed the instructions to run the sample?

Thank you for the answers.

TomPie posted this 29 June 2013


there seems to be a problem in the iOS example. It's trying to activate an 'installationId' before submitting the HTTP requests which IMHO is not necessary.

Change the method

activateInstallationWithDeviceId in


and it should work.



  • Liked by
  • Anastasia Galimova
Anastasia Galimova posted this 01 July 2013

Thank you for the solution! The developers confirmed it is a bug. The sample code should be fixed this week.