Andreas Schacherbauer

said
over 4 years ago

Today I received your test results with the custom SDK that you send us via mail. I will write the answer only in the forum since more people can benefit from it. The additional log output was somehow expected but doesn't bring me closer to a solution.

Can you please tell me if you're calling any Wikitude iOS SDK API from within an dispatch_async block? Maybe you can post the complete view controller impl. so that I can see the overal SDK usage.

As I don't have an iPhone 5 running iOS 8.0.2 it's a little bit hard to debug. Can you reproduce the issue on any other device/iOS combination?

Best regards

Andreas

N

Nigel Grange

said
over 4 years ago

Hi,

No, it's not being called within a dispatch_async block. I have also tested on both iPhone 5 / iOS 7.1 and iPhone 6+ / iOS 8.1 and everything works correctly, the problem only occurs on the iPhone 5 / iOS 8.0.2. (I haven't tested other devices with iOS 8.0.x).

Nigel Grange

I have tested with the custom framework provided, and have nailed the source of the problem.

The error messages reported by the library are:

architect view encountered internal error: Error Domain=com.wikitude.architect.services.camera Code=106 "Error creating device input for camera position '1'. ('Error Domain=AVFoundationErrorDomain Code=-11852 "Cannot use Back Camera" UserInfo=0x199ae320 {NSLocalizedDescription=Cannot use Back Camera, AVErrorDeviceKey=<AVCaptureFigVideoDevice: 0x199a8750 >, NSLocalizedFailureReason=This app is not authorized to use Back Camera.}')" UserInfo=0x199ae340 {NSLocalizedDescription=Error creating device input for camera position '1'. ('Error Domain=AVFoundationErrorDomain Code=-11852 "Cannot use Back Camera" UserInfo=0x199ae320 {NSLocalizedDescription=Cannot use Back Camera, AVErrorDeviceKey=<AVCaptureFigVideoDevice: 0x199a8750 >, NSLocalizedFailureReason=This app is not authorized to use Back Camera.}')}

The cause of the issue is not iOS 8.0.2 specific, but that the app was denied permission to use the camera. This of couse can be checked in our app before instantiating the WTArchitectView, though of course it is an improvement if this error can be detected and reported by the Wikitude library (or at least not crashing when this error occurs).

Thanks very much for your help is solving this issue.

A

Andreas Schacherbauer

said
over 4 years ago

Hi Nigel, Thx for reporting, testing and also finding the issue! We will definitely improve the error handling in the next SDK release.

Just one more question: Did the SDK crash with the latest .framework you had? Have you tried to call -start with a @try @catch block?

Best regards

Andreas

N

Nigel Grange

said
over 4 years ago

No, the latest framework didn't crash after showing the error message in the console. It just showed a blank screen as would be expected if access to the camera has not been authorised.

A

Andreas Schacherbauer

said
over 4 years ago

Perfect, than this will be part of the SDK 4.1 which will be release beginning of 2015.