Community

• 

  Oksana Serdyuk

  • October 12, 2017 07:44

   
  Hello,

  We have not faced this issue before, so to be able to help you we need more details about the error. Please send the following additional information to SDK_Support@abbyy.com:
  1) What version of RTR SDK do you use: free or extended? If the second one, then kindly specify your serial number.
  2) Also, please specify the build number of RTR SDK, which you can find in the Readme.html file included in the distribution.
  3) What iOS version are you using/testing on?
  4) Do we understand correctly that our standard sample works correctly? If so, is it possible to get from you a sample project, based on our standard code sample, with made needed changes for reproducing the issue?
  5) Please describe the issue in more details. You can attach some screenshots and logs for illustrating the problem.

  No 0 Yes
• 

  mobilu

  • October 12, 2017 07:54

  Hello,

   

  we are using the free version since we are still evaluating the library. Right now we are using version 1.0.7.56 which should be the latest.

  We made another discovery: Apparently the issue only comes up since we created an internal cocoapod for the library. If we include it directly everything is fine.

  Being able to include the library as a cocoapod is essential for us since we will have it conditionally enabled on a per client basis (since the framework is really big). Is there an official cocoapods spec that we could use (even if it's just for paying customers)?

  We also had to include the CoreMedia framework to successfully build the cocoapod. Does the SDK link against any other unmentioned libraries other than c++? Perhaps we are missing something there.

  ios is version 10.3

  The project is working again as soon as we include the framework directly (not using cocoapods) but this makes it hard to manage for us.

  Best regards,

  Mobilu Team

  No 0 Yes
• 

  Oksana Serdyuk

  • October 13, 2017 08:19

  The developers say that it should be possible to use RTR via CocoaPods. In order to give you some specific recommendations they ask to send us your podspec file – the file with the settings where the library is located (https://guides.cocoapods.org/making/private-cocoapods.html).

  No 0 Yes
• 

  mobilu

  • October 13, 2017 09:38

  To be honest I am not used to this kind of response (most closed source library developers don't care for cocoapods).

  here's my podfile:

  Pod::Spec.new do |s|
    s.name         = 'ABBYY'
    s.version      = '1.0.7.56'
    s.homepage     = 'https://www.abbyy.com/en-eu/mobile-ocr/iphone-ocr/'
    s.license      = 'MIT'
    s.author       = { 'Mobilu' => 'team@mobilu.lu' }
    s.summary      = 'ABBYY SDK'
    s.description  = 'ABBYY SDK Pod for Mobilu'
    s.platform     = :ios, '8.0'
    s.source       = { :git => 'https://github.com/axelline/ABBYY.git', :tag => s.version.to_s }
  
    s.resources 		= 'assets/Dictionaries', 'assets/Patterns'
    s.vendored_framework	= 'AbbyyRtrSDK.framework'
  
    s.library       = 'c++'
    s.xcconfig      = { 'FRAMEWORK_SEARCH_PATHS' => '"$(PODS_ROOT)/ABBYY/**"',
  		      'LD_RUNPATH_SEARCH_PATHS' => '"$(PODS_ROOT)/ABBYY"' }
    s.frameworks    = 'CoreMedia'
  
    s.requires_arc = true
  end
  

  Thanks for the great support,

  Matthias Kutscheid, Mobilu

   

  No 0 Yes
• 

  Oksana Serdyuk

  • October 16, 2017 09:01

  Hi Matthias,

  our developers recommend to try to add:

  s.pod_target_xcconfig = {
      'OTHER_LDFLAGS' => '-lc++',
  }

  No 0 Yes
• 

  mobilu

  • October 16, 2017 09:55

   Hi Oksana,

   

  thanks for the hint, but unfortunately the issue still persists.

   

  We also tried dragging lib c++ into our project directly, as well as the dependent files so that the only thing that remains is the framework itself. Unfortunately none of those measures resulted in running code.

  We only get the issue above when we feed the recognition service, which means the build runs just fine.

  No 0 Yes
• 

  Oksana Serdyuk

  • October 16, 2017 10:03

  Please compare how our Mobile Department uses the RTR library via CocoaPods:

  Pod::Spec.new do |spec|
  
    spec.name = 'AbbyyRtrSDK'
  
    spec.version = '1.0.7.56'
  
    spec.license = { :type => 'ABBYY', :file => 'ABBYY' }
  
    spec.homepage = 'http://www.rtrsdk.com'
  
    spec.authors = { 'ABBYY SDK' => 'sdk@abbyy.com' }
  
    spec.summary = 'A pod wrapping RTR SDK'
  
    spec.platform = :ios, '8.0'
  
    spec.source = { :svn => '', :revision => '' }
  
    spec.vendored_frameworks = 'AbbyyRtrSDK.framework'
  
    spec.resources = 'Dictionaries', 'Patterns'
  
    spec.frameworks = 'Foundation'
  
    spec.libraries = 'c++'
  
    spec.requires_arc = true
  
    spec.pod_target_xcconfig = {
  
      'OTHER_LDFLAGS' => '-lc++',
  
      'HEADER_SEARCH_PATHS' => '${PODS_ROOT}/#{spec.name}/**'
  
    }
  
  end
  

  No 0 Yes
• 

  mobilu

  • October 16, 2017 11:58

  We still need CoreMedia to even validate the spec.

  We are still running into the same crash wtih teh following spec:

  Pod::Spec.new do |s|
    s.name         = 'ABBYY'
    s.version      = '1.0.7.56'
    s.homepage     = 'https://www.abbyy.com/en-eu/mobile-ocr/iphone-ocr/'
    s.license      = 'proprietary'
    s.author       = { 'Mobilu' => 'team@mobilu.lu' }
    s.summary      = 'ABBYY SDK'
    s.description  = 'ABBYY SDK Pod for Mobilu'
    s.platform     = :ios, '8.0'
    s.source       = { :git => 'https://github.com/axelline/ABBYY.git', :tag => s.version.to_s }
  
    s.resources     = 'assets/Dictionaries', 'assets/Patterns'
    s.vendored_framework  = 'AbbyyRtrSDK.framework'
  
    s.library       = 'c++'
    s.pod_target_xcconfig      = {
      'FRAMEWORK_SEARCH_PATHS' => '"$(PODS_ROOT)/ABBYY/**"',
      'LD_RUNPATH_SEARCH_PATHS' => '"$(PODS_ROOT)/ABBYY"',
      'OTHER_LDFLAGS' => '-lc++',
      'HEADER_SEARCH_PATHS' => '${PODS_ROOT}/ABBYY/**'
    }
    s.frameworks    = 'Foundation', 'CoreMedia'
  
    s.requires_arc = true
  end
  

   

  No 0 Yes
• 

  Oksana Serdyuk

  • October 17, 2017 07:47

  To continue investigation of the issue, we have to ask you to send us more details:
  1) Please share your full project or a simplified sample project which we can use on our side for reproducing the issue. Also please provide us with a step-by-step instruction that will allow us to replicate this situation.
  2) At what exactly moment does the issue occur? Do we understand correctly that the issue does not depend on an image you recognize?
  3) Please send the logs obtained when the issue happens.
  4) Is it so conceived that we cannot find the https://github.com/axelline/ABBYY repository specified in your podspec file?

  No 0 Yes
• 

  mobilu

  • October 17, 2017 07:59

  about point 1: it's a fairly complex project, but we'll see if we can cut it down to demonstrate the issue (maybe even with your demo project)

  point 2: it does not depend on any image we try to recognise. The library crashes with the first received buffer from the live image. 

  Point 3: At this point there is absolutely no logging output. The last thing we get is "the search region is invalid", but for some reason we even get this line with the library directly in the project and it only appears for the first call.

  point 4: This is a private github repository. If you want to test with it directly I can make it public for some time. (Edit: it's public for now, but you will have to validate and build the spec yourself since using the pod will depend on another spec repository which contains some more libraries that I cannot make public)

  No 0 Yes
• 

  mobilu

  • October 18, 2017 08:02

  Here's our test project. It looks like our issue is that we are using the framework in one of our frameworks.

  https://mobilu-team.s3.amazonaws.com/sample-textcapture-swift.zip

  We have a framework that we re-use in other in house applications that supports a lot of features and we usually embed custom libraries there.

  Can you tell us what we have to do in the parent project to fix this?

   

  Best regards,

  Matthias

  No 0 Yes
• 

  Oksana Serdyuk

  • October 20, 2017 13:53

  Matthias, unfortunately, we have no CocoaPods specialists at the moment and it may take long time to investigate the issue. As I wrote, our Mobile Department uses successfully the RTR library via CocoaPods in some solutions, and their podfile is given above. Please try first to use similar settings only for RTR and then, when you are success, try to add CoreMedia.

  I am extremely sorry, but this is all we can recommend for this case now.

  No 0 Yes
• 

  mobilu

  • October 20, 2017 14:03

  Dear Oksana,

  we used your settings from above and were not able to build the pod without the coremedia addition. (which means the file from above is not working for us, maybe because your colleagues use a different cocoapods version).

  No real issue for now, it would just be nice to be able to pull this library in as a pod since right now all our developers have to have it as a local copy.

  No 0 Yes
• 

  Oksana Serdyuk

  • October 23, 2017 08:31

  FYI, our MD uses Version COCOAPODS: 1.2.1.

  No 0 Yes

Please sign in to leave a comment.