Same problem. And I used .destroyAll() to remove 6 GeoObject.
Same problem here, any solution??
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.
Hi Wikitude!, any news about question?, I have the same trouble :( "Failure to deallocate CLLocationManager on the same runloop as its creation may result in a crash"
this problem has been fixed and will ship with the next minor release of the SDK.
How can I fix the problem before the next minor release of the SDK?.
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.
Hi Daniels?, any news?.
we had some issues with the nightly build recently. Today's build completed successfully again. I'll upload the package tomorrow morning and provide a link to it here.
My apologies for the delay.
Good morning Chris,
you can download the pre-release SDK package including the aforementioned fix here.
Please review the files attached. I still have the same problem.
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
2 people have this problem