Vivoactive: launcher icon disappeared

How often do you see this? I saw it once (I think it was when I hit "download" on something that was already installed to get an update, when I should have done an uninstall-reinstall or used GE to get the update - I'm on Android) I've never seen it reported by any users for my apps.

Does it happen when there is a sideload installed and then it's also installed from the store or something?

Mostly when sideloading .. but have had a user have the same thing in the Connect IQ Store. He reinstalled the app and it worked then. I knew it was not the app as it was working fine for me.

But I just reinstalled my Eclipse environment (and copied and pasted my project and it is there now. This seems to be the part that fixed it, not the environment as it still had issues after the Eclipse refresh). So we shall see how things work out. I learned today how to quickly fix my environment .. so it is not a big deal now.

I have sometimes had success with changing the version of the SDK used to build a project and sometimes the launcher icon would just reappear. But there is definitely something going on that Garmin should look at. But I think that it would be really hard to nail down a cause.

The problem today .. happened when I removed a bitmap from the drawables folder. Before that it was fine. So .. something is not right cause after that the launcher icon refused to show up.

It's more than likely that it has nothing to do with the version of the SDK or the Eclipse you use, but a conflict (based on UUID) of what's on the watch.

There are 16 "slots" on the watch where it saves info on the CIQ "things" on the watch. If you have ABCD1234.prg on your watch from the store and then sideload MYPROG.prg that is really the same (based on UUID), things get confused on the watch. The same kind of thing might happen if ABCD1234.prg from the store is on the watch, and you hit download in the store and get DEFG6789.prg on the watch. The watch is trying to make sense of two versions of the same thing.

Granted, somewhere this probably should be prevented, but there seem to be ways to avoid it. (don't hit download on something already installed, delete the store version before sideloading, or delete the sideload before downloading from the store, for example)

It's more than likely that it has nothing to do with the version of the SDK or the Eclipse you use, but a conflict (based on UUID) of what's on the watch.

There are 16 "slots" on the watch where it saves info on the CIQ "things" on the watch. If you have ABCD1234.prg on your watch from the store and then sideload MYPROG.prg that is really the same (based on UUID), things get confused on the watch. The same kind of thing might happen if ABCD1234.prg from the store is on the watch, and you hit download in the store and get DEFG6789.prg on the watch. The watch is trying to make sense of two versions of the same thing.

Granted, somewhere this probably should be prevented, but there seem to be ways to avoid it. (don't hit download on something already installed, delete the store version before sideloading, or delete the sideload before downloading from the store, for example)

Sorry .. don't buy the UUID thing at all. Because if that was the case it would not have worked from the start .. and it worked fine until I deleted that bitmap. This was not a copied project from a previous project, it was 100% new from scratch. I never touched the store or synced all day.

But did you already have a .prg with the same UUID on the watch and then sideload a new version with the same UUID?

You're seeing something that isn't common and I'm just trying to help narrow it down.... I copy a new sideload for something every day or two, including changes to launcher_icon (that's how I see how it really looks), and just don't see it happening for me (other than that one time where I had 2 .prgs with the same UUID on the watch that I mentioned before)

But did you already have a .prg with the same UUID on the watch and then sideload a new version with the same UUID?

No .. it was a 100% new app, built from scratch that had only been sideloaded. Could it have the same UUID as another app .. very doubtful as my odds of winning the lottery are probably about the same.

Thanks so much for jumping back in on this thread. I tried a couple things here this morning to sniff out the UUID hunch and I'm not thinking that is what is going on. I'd love to get some more info and open up a ticket to investigate. If you are willing sending me a detailed description and the project folder or snippets of code that you think are related to it would be super helpful. You can send them to [EMAIL="[email protected]"][email protected][/EMAIL].

-Coleman

Coleman ..

There is nothing that I can really add .. but think that there is something going on when a bitmap is deleted. The launcher icon is definitely being detected as if you rename it, you get an error etc. But it is just weird that this problem rears up on occasion. I am not the only one that has seen this either as you can see above. I have had it .. on 2 or 3 occasions. It is interesting that both instances are with Vivoactive devices (in my case a VAHR).

I did the following as far as I can recall ..

- removed power.png bitmap file from drawables folder.
- removed mPower1 = Ui.loadResource(Rez.Drawables.power1);
- removed <bitmap id="power1" filename="power.png" /> from drawables.xml
- removed dc.drawBitmap(77, 182, mPower1);

I did reinstall my Eclipse Mars environment and make sure that there were no updates that were not installed. But that did not fix the problem.

I did fix it .. by copying my project to another name, and then deleting the old one and then copying it back to the old name. It then worked. I did not have any problems initially when the project was created and side loaded. It was only after this part, and it is working fine now.