CIQ App Store claims 2 of my apps now have the same AppID

I have 4 clones of a simple data field app. (I know >_>). I submitted the original a month ago and it worked fine. The second was submitted 2 weeks ago, and it worked fine.

The 3rd and 4th were originally submitted two days ago.

I know that I didn't originally submit identical IQ files for the 3rd and 4th because:
- The AppName is different (i.e. the name that shows up when you choose the data field on the watch)
- The apps can write data to FIT files. The label and graph colour are different for each of the apps.
- I was able to install them at the same time, on a single watch

Tonight I made an update to all four clones, and rebuilt everything. Uploading new version for clones 1-3 worked fine.

But when I tried to update clone 4 with the corresponding newly built IQ, the store claimed the AppID was different than what was originally submitted.

The following errors were detected in your app file
The app-id within the manifest-file deviates from the one originally registered for this app.

When I updated clone 4 with the newly built IQ from clone 3, it was accepted. So now I apparently have two copies of clone 3 in the store!
(I should never have tried that, but I just had to find out...)

Is it possible that I messed something up here? I checked my archives of the original submission for clone 3 and clone 4: the manifest IDs are different and they are what I expect to see. (I generated them using the UUID generator suggested in a garmin dev doc.)

Now clone 4 in the store has the wrong IQ file (from clone 3).

I just did a test with both (non-updated) fields on my watch, with writing to a FIT file, in the same activity. The labels and graph colours are what I expect to see (i.e. different from each other). Meaning that the original versions of clone 3 and clone 4 were distinct, and came from the correct IQ files.

Is there any way to force the store to accept the correct IQ?

(On a side note, I once accidentally submitted the IQ for clone 1 to the clone 2 store entry and vice versa, yet the store did not complain). All 4 of the clones have different AppIDs (or they did, anyway).

Links to the apps in question:
http://apps.garmin.com/en-US/apps/e9...5-f436909377dd
https://apps.garmin.com/en-US/apps/1...d-e1e81cb38e8a

The next thing I will try is to update both apps on my watch and test them out, but frankly I'm a little worried about what the results will be. There's no way they can work properly now, since literally the same IQ has been uploaded for both.

Here's a side-by-side screenshot which shows different store URLs, but identical AppIDs:

http://image.ibb.co/j7Gkzv/dfKYCQh.png

Edit: I renamed the IQ files in question to .ZIP and compared the manifest.xml files within. Everything matches my expectations.

jim_m_58 over 8 years ago

It sounds like there is a bug in the store and Garmin can look at it, but the fastest thing to do is what it sounds like you did. Remove #4 and re-add it with the #4 appid.

HerrRiebmann over 8 years ago

It sounds like there is a bug in the store and Garmin can look at it[...]

I bet, like the not updating fitContributor-bug from 2016, it is not in hands of CIQ Team...

Former Member over 8 years ago

Hey,

I've got this reported to the Store Team. They are usually pretty quick to help out. I'll update as soon as I know more.

Thanks,
-Coleman

flowstate over 8 years ago

Hey,

No worries. I will say that I've already removed the broken app and resubmitted it, and the turnaround was 2 days. It's fine because:
- It's the 4th clone of an app that's only used by a small number of people
- I initially broke it a couple of days after the original submission.

I didn't want to leave the 4th clone in the bad state where it conflicted with the 3rd clone. (Although that part was probably my fault. Once the appID was bad, I should not have purposely tried to update the app with the wrong IQ file.)

It also seems like this has happened before, and it has recently happened to someone else:
https://forums.garmin.com/forum/deve...rom-1-year-ago

Thanks.

Former Member over 8 years ago

We have seen this issue periodically. It may be related to updating multiple apps at the same time in different tabs. We think (not tested or proven yet) that there might be a global state that is cached when uploading an app on the browser side that gets updated when you push the second app after the initial ID check. Again, that's all conjecture, but we sniffing that out to see if that is the cause. I'm not sure how you were uploading the multiples of your app or if this matches your process in any way, but perhaps that provides a little clarity. We are going to continue to investigate on our end.

Thanks,
-Coleman

flowstate over 8 years ago

Hey,

Yeah, I think that's what may have happened. I definitely had 2 tabs open.

The (unintentional) workflow may have been:
1) Upload App 1 in tab 1, without submitting details.
2) Upload App 2 in tab 2, without submitting details
3) Submit details for App 1 in tab 1.
4) Submit details for App 2 in tab 2.

I think it may have been in step 3 or 4 that App 1's ID was applied to App 2. I didn't want to try to recreate the process (for obvious reasons), so I was never sure.

Now when I update multiple apps, I make sure I only have one tab open.

Thanks for the update.