Start a new topic

WTSimpleARBrowser mistakes

WTSimpleARBrowser mistakes


I have tested the same app with the same configuration in an iPhone 4 running on iOS 5 (where it didn't worked) and in another iPhone 4 running on iOS 6 (where it worked)




It shouldn't matter if you're using iOS 5 or iOS 6. Have you tested it on both os at the same time and at the same location?


Best regards


What about my question? Should the examples work on iOS 5 as in iOS 6?

What does the current CLLocationManager use as settings? 
For example: self.locationManager.desiredAccuracy = kCLLocationAccuracyBest;
But okay, that makes it quite transparent for us, thanks!

Maybe insert a feature in the next SDK to tweak these settings? :)


The SDK uses an iOS CLLocationManager object to retrieve location updates. Currently you cannot influence the internal CLLocationManager settings.

You can create your own CLLocationManager object and inject the location into the Wikitude SDK. 


Best regards


Hey Wolfgang,

How sure can we be that the Location updates, I didn't find a setter on the architectview to tell it how many times it has to update. Do you use an internal CLLocationManager for updating the location or are you using the HTML5 Locations?
When we're "in the field", we find that sometimes it's not updating for several 100's meters, is there a setting we can put on the updates of the locations? Like in iOS you would put "BestForNavigation" etc?

Or you think in that case it's better to run our own instance of the CLLocationManager and inject the new locations to the ArchitectView?


Same happens with the alert. I can see it in the device with iOS 6 but not in the one with iOS 5


I have realised that it only doesn't work with iOS 5. It works with iOS 6. Is that how it should be?




Please check following things:

The following defines are set to your current location:







use a service like to verify the location.


Add following code to the archtiect world to see what location is reported by iOS


AR.context.onLocationChanged = function(latitude, longitude, altitude, accuracy){

alert('lat: ' + latitude + ' lon: ' + longitude + ' alt: ' + altitude);



This will output an alert each time the location changes and will let you know the exact location used. Compare that to the location you defined.


Keep in mind:

- this is only a sample, the defines are only used to create 50 points around that location

- in a real application all POI locations should come from real world location


Let me know if you have further questions

Yes, it looks like it is not updating the location of the mobile... 

I made this change because, if I understood well, per default it is 50km, and I wasn't seing any of the 50 points created by default. I checked some of them, and they were inside the 50 km radius.

Can you think in any reason why this is happening?

This basically tells the architect view to render all POI's within 100 km radius.
So if you're poi's are within that, they will show up, otherwise not ^_-

No. I have made it work adding this. ;

Should it work as well without this?


Do you have location restrictions on?


I'm facing the same issue. I haven't created my own world. I'm just using the one given by the app, but it is not showing any point. I have checked all what was said in the previous messages as well.

Login or Signup to post a comment