Start a new topic

Failure to deallocate CLLocationManager on the same runloop as its creation may result in a crash

Hello,


When I call .destroy() on a AR.GeoLocation object, I am getting the following warning in my iOS console log:


Failure to deallocate CLLocationManager on the same runloop as its creation may result in a crash


True to it's word, if I do this enough time the whole apps crashes. I am using the new 6.1 iOS javascript SDK. Is there a way I can avoid this? For now I'm simply not destroying AR.GeoLocation objects. 


Thanks.


2 people have this problem

Hi Andreas;


I'll check it and get back to you.


Regards.


Chris.



???

Hi Christian,

I just had a look at the fix Daniel implemented and it works fine for my test case. 

To avoid any misunderstandings, could you send us a demo Architect World with we can use to reproduce your particular problem?


To verify the build you're using, can you please send us the log output of the following snippet? `NSLog(@"Architect is running with version %@, generated at %@", [WTArchitectView sdkVersion], [[WTArchitectView SDKBuildInformation] buildDate]);`


Best regards,

Andreas

Hi Andreas;


Please see attached file.


Regards.

Hi Christian,

that's what I expected.

Could you send us a demo Architect World or is this happening with one of our examples as well?


Best regards,

Andreas

Andreas;


Daniel sent me a link with the fix version and I am using that but I have the same problems.


I am using for testing: iPhone 6 with 10.3 OS, iPad mini 2 10.3 OS and iPhone 5S 10.3 OS.


Regards.



Hi Christian,

I understood that you use the pre-release version we send you earlier this week, but I don't know if you use one of the Wikitude SDK examples or your own Architect World.

Could you please tell me if that happens with one of the Wikitude SDK example or with your own Architect World.


Best regards,

Andreas

Andreas:


I'm not using my own architect world, I'm using your samples: ReloadingContent.


Please watch video: https://youtu.be/Lr5flqSmZng


Regards.


Chris.

Hi Chris,

thx for the detailed explanation. Now I was able to reproduce it one one of our devices as well. I get back to you as fast as possible.


Best regards,

Andreas

Hi Chris,



this problem has been fixed and will ship with the next minor release of the SDK.



- Daniel

Hi Daniel:


How can I fix the problem before the next minor release of the SDK?.


Thanks.


Chris.

Hi Chris,



I'm afraid you cannot. This issue requires a new build of the SDK. I can, however, provide tomorrow's nightly build for you to use in the meantime if you cannot wait for the official release.


Be aware, though, that nightly builds have not yet undergone most of the testing rounds we go through when releasing a new version of the SDK. So some instability is expected. Having said that, the current development state should be quite stable. Not guarantees, obviously.



- Daniel

Thanks Daniel!.


Chris.

Hi @all,

thx for reporting this issue and sorry for the delayed answer. I created an internal bug report and we will have a look at it asap.


Best regards,

Andreas

Same problem here, any solution??

Login or Signup to post a comment