• Replies 5 replies
  • Subscribers 18 subscribers
  • Views 946 views
  • Users 0 members are here
Options
Related

Any way to change duplicated Manifest AppID after a data field has been published?

ekutter-dnu
I somehow uploaded two data fields with the same Manifest AppID. Not sure how that happened as each one has a different number in the manifest.xml file, unless I somehow specified the wrong .iq file to upload when I submitted the second field. It's basically the identical data field as two versions to allow someone to have two instances with different settings.

It seems to work having both CIQ fields installed and each one has its own settings. Will sharing a Manifest AppID cause problems? is there any way to change it now?

If it is OK to have two with the same Manifest AppID, but different data field names, can I achieve having two identical, but individually configurable, fields by just using the same .iq file with different app names as seems to be happening right now?
  • The app store (and I believe the device itself) should prevent two apps having the same appid installed simultaneously.

    Even if it is possible to have multiple apps with the same appid, it would be a bad idea. The platform won't be able to tell one app from the other and would potentially route information to the wrong one.

    Travis
  • I just looked at the .prg files installed on my device after downloading them both from the store. Indeed they do have different (and the correct) Manifest AppID #'s as shown in my code. I just looked at the binary version of the files and found the ID at byte offset 60. Is there a tool that would have done this?

    But in Garmin's database for publishing, it seems to have the same ID for both "Big Numbers" and "Big Numbers Pg2". So it won't let me publish an update for the 2nd because the file I'm publishing's Manifest AppID doesn't match what Garmin thinks it should be. Further, both data fields show the exact same Manifest AppID # on the Edit App Details page for publishing.

    Garmin support, could you figure out why the publishing web site has the wrong Manifest AppID for Big Numbers PG2 and does not match the actual data field file.
  • Former Member
    Former Member
    Hey ekutter ,

    In order to fix this, we will need to have the UUID for each data field and which one it should be associated with (i.e. the store link). We can then have the app store team adjust the database. Most often when we see this, it's caused when a developer is uploading multiple apps or updates to them and has multiple browsers or tabs open to do this. It usually goes something like this:

    1. Sign into account
    2. Open up a tab with each app in it
    3. Select to upload a new version of each app
    4. Set version numbers and try to upload

    ...then the upload fails on the second one. For some reason, browsers are caching the info and feeding something wrong to our database. We are working on a way to fix this so that it doesn't happen, but we suspect that the browser is holding onto the first file's id number somewhere and blocks the second upload.

    TL;DR - If you can get us the UUIDs with the links to the correct datafields, we should be able to edit the database and free you up to make updates.

    Thanks,
    -Coleman
  • Yep, that sequence sounds about right. Thanks.

    This one is correct
    https://apps.garmin.com/en-US/apps/d3347345-4afe-474b-a405-3073c17c7a55
    5EFD1BD028F64849967F50DDE12DBD03

    This one is broken
    https://apps.garmin.com/en-US/apps/347919ae-cd01-4e41-81f9-d3652144cacd
    75c2f696bfba490e93c9a22c9132178b
  • Former Member
    Former Member
    Fantastic. I've emailed the store team to get this fixed.

    - Coleman