Log in or register to post comments

Possible Network Problem Bug

September 4, 2013 - 2:55am #1

Vuforia SDK Version: 2.6.7 (Unity) -

Description with steps to reproduce:

Hi there,

we've created an AR app that our client reports works just fine (iOS and Android) except on one device, a Samsung Galaxy Tab 2 10.1 (GT-P5110) running Android 4.0.3. Our (custom) splash stays on forever and Unity doesn't show up.

When we received the device to test it at our office, the very same app worked just fine, so here's our assumption:

At their venue, they probably have a bad WiFi connection (maybe with a heavy firewall), that causes Vuforia to timeout/or hang on getting the device specific data it loads from the Qualcomm servers. Here at our office it startet both with WiFi on or off.

So to undergrid or disprove this theory, could you explain how Vuforia usually should behave on a network timeout? how long does it wait for the data to arrive before it proceeds?

Thanks a lot in advance,



Development OS (Mac OS X, Windows, Linux): Mac OS X Mountain Lion -

Mobile OS and Version: Android 4.0.3 -

Mobile Device Manufacturer and Model name: Samsung Galaxy Tab 2 10.1 (GT-P5110) -

Do the Vuforia Sample Applications show the same behavior?: Again, at our office it works. We couldn't test it at our clients office yet, but we're planning to do that.

Possible Network Problem Bug

September 5, 2013 - 5:27am #6

Thanks for the clarifications. 

If you are referring to the device -specific profile download, this is not something that should prevent your App from running, as Vuforia can use automatic/default settings when there is no network.

So, the network timeout error you see should not be cause by Vuforia, unless you are using the Cloud recognition feature.

Certainly we can put this on hold, as you ask... and when you have more findings feel free to share.


Possible Network Problem Bug

September 5, 2013 - 3:06am #5

The Data Set is also bundled (in the StreamingAssets just like it is with the demos). 

What i was referring to is the device specific tracking settings that Vuforia tries to load upon start. I read somewhere (forums or docs), that Vuforia has a big database of devices and device specific settings to optimize the tracking for each device.


Anyways, since I'm not able to reproduce this exact error I suggest to put this one on hold until we (me and our client) can reproduce it and deliver more information on it.

Thanks for your support!

Possible Network Problem Bug

September 4, 2013 - 9:31am #4

OK. so, can you describe the eact application behaviour ?

are you downloading a dataset from a server into your device storage ?


Possible Network Problem Bug

September 4, 2013 - 9:15am #3

i should have mentioned that it doesn't use cloud recognition, just  a bundled data set.

Possible Network Problem Bug

September 4, 2013 - 6:31am #2

Thanks for your report.

In general, Cloud Recognition apps require an Internet connection to work. The perceived recognition delay of a target may depend on the speed of the network connection. We recommend using a 3G or WiFi connection, slower connections can lead to degraded performance

So, a slow network connection (possibly also combined with heavy firewall as you suggest) can certainly lead to network error such as the newtork timeout that you observe. However we cannot provide exact values on the time out (although you can practically get a measurement of such time by observing the waiting time with your app, before the error is raised)



Log in or register to post comments