Log in or register to post comments

Could not start tracker

July 29, 2014 - 2:30am #1

I don't see any issues happening during our internal tests, but having launched the app on iOS...and watching the analytics which captures errors...I see thousands of cases of an error "Could not start tracker".

I don't know how vuforia handles this error. The error is too vague (if anything, you could update the error message).

It could be serious and means the app isn't working for a percentage of our users. It could mean that vuforia just tries again and eventually starts the tracker. I don't know (the error is too vague). Please ask the dev team to indicate which thing is happening. And if it's the first one, then how to resolve....or detect...etc.

The analytics data indicates it happens on a broad range of hardware.  The SDK is version 287 and the Unity version is 434

Could not start tracker

August 23, 2019 - 8:48am #8

very tough to to handle unity 2019 compare to older version. ples explain why came continuous error.. and ples replay how to solve tracker error

 

Could not start tracker

July 31, 2014 - 9:42am #7

Well...the app works. It passed our QA tests, and Apple's.  And...there isn't a flood of comments about it not working...so...it must be working. I feel like if it were a real failure case, then I'd be hearing about it somehow.

But none the less there are thousands of these errors in our analytics log. There is also a lot of errors about datasets not loading ( which are also setup correctly ). So in the scope of that, the error makes sense. What doesn't make sense is why datasets wouldn't load, or why the tracker would be trying to start again.

At some point, probably before we launch Android, I'll try to expose this...just so I can know what the deal is.

Another alternative, is that if someone over there wants, we can do a skype with screen share so you could have a look at the project and see if something looks wrongly setup. 

 

Could not start tracker

July 31, 2014 - 9:27am #6

The message "Could not start tracker" is self-explantory, in that it indicates that the Tracker start operations failed.

As Moises already answered (from an engineering perspective),

A tracker may not start if the camera was not started before trying to start the tracker or if the dataset is not present.

In addition, I can add that another reason could be the Tracker was already started and possibly the app for some reasons simply tries to start it again (in which case, this would be harmless).

But without a reprodubile test case and/or some clear error logs  it is hard to make any hypothesis and determine what exactly occurred in the App when the message was thrown (and thus assess if the problem is "serious" or not).   

The only piece of information that seems to suggest a reasonable answer (e.g. probably an occasional / minor issue, not something systematically happening) is what you say in this:

Internally, for testing, it doesn't appear at all, in any platform. I get the feeling it's uncommon, but with a large DAU of course that becomes thousands of cases which is what we're seeing.

 

 

 

Could not start tracker

July 31, 2014 - 8:42am #5

It could also be present in Android, but we haven't launched Android yet. Right now we're focused on iOS.

Internally, for testing, it doesn't appear at all, in any platform. I get the feeling it's uncommon, but with a large DAU of course that becomes thousands of cases which is what we're seeing.

Can you please answer the question I asked 2 days ago? Since I can't test it...can you tell me...what vuforia does when this happens...does it just fail...or try again. Is this a benign issue or something serious?

 

Could not start tracker

July 31, 2014 - 5:15am #4

You mentioned iOS in your first post;  can you confirm this is iOS only ?

Could not start tracker

July 31, 2014 - 4:11am #3

This is for a live game that has a significant amount of traffic. Its featured in your gallery.

The first question should be, is this is a harmless debug message or it means those users can't use the app as it is now. Which is it? That was the question I asked you. Can I get the answer? You will need to ask a developer on the team about the error message.

I don't know if it's happening for 3.0. As I said, this didn't seem to occur in our tests prior to launch. So...even if I tried it on 287 in some controlled test...I don't expect it to happen.

Can I reproduce it in one your samples? I could authorize the resources to do that work, but first you need to answer the question I asked. Obviously if it's a harmless thing...then we don't do that work. I don't see a ton of 1 star ratings, so I assume it's harmless...but i'm trying to find out.

Which tracker am I using? It's a standard ImageTarget setup. Pretty much exactly like your most typical example. But the app also has a UDT feature, which is a little more exotic. Since the error message is so vague...it's difficult to know what is happening. It could be related to one or the other or both. Again..you need to ask the dev what it means.

The bit about the camera start order and datasets...all of that stuff is setup correctly. What's interesting though is that I also see error messages about failed to load xyz dataset..but it's setup correctly and does load in our tests (and obviously many people are using the app). I also see a message "An invalid object handle was used."...sounds related.

Again, I'm hoping what vuforia is doing, is just occasionally failing to start because of some timing issue, and just tries again...ie harmless. Please let me know the answer to that very important and primary question.

 

 

 

Could not start tracker

July 30, 2014 - 5:42pm #2

Hi,

Could you provide more information about this issue? Is this happening also for 3.0? Which tracker are you using? Can you reproduce it in one of the samples?

A tracker may not start if the camera was not started before trying to start the tracker or if the dataset is not present.

Log in or register to post comments