Mystery AppVersion showing when App is uploaded to Connect Store

Jeff over 5 years ago

A "Version" is displayed after I upload an updated build of my app to the App Store (see screen shot).

That string dos not appear in my code, or in my settings, properties, or string resources.

Can anyone tell me where it's coming from and how to make it match my actual version ?

Thanks

Jeff

0 jim_m_58 over 5 years ago

Are you sure that something wasn't mistakenly used from the list you'll see when you enter the version on the same screen where you specify the .iq file to upload? I've done that before, and just reloaded the same iq file with the correct version

0 Jeff over 5 years ago in reply to jim_m_58

I tried it again.

The area I've shown in the screen shot shows the LAST string entered for version, not the one just entered.

0 jim_m_58 over 5 years ago in reply to Jeff

There's been something odd in the store where when you send a new version, it doesn't take effect for a few minutes.

See forums.garmin.com/.../psa-please-double-check-your-uploads-if-you-are-uploading-anything-today

0 Jeff over 5 years ago in reply to jim_m_58

Thanks Jim

0 Jeff over 5 years ago in reply to jim_m_58

Hi Jim,

This is a continuing problem and it is not an issue with the version of the App that is available to me for download after a I've uploaded a new version. This is a continuing issue with the upload process's handling of the version string that is provided.

From my point of view there are two issues.

1) The upload process insists on using the last version string that was entered. I am now "fooling" it, but it's an ongoing issue and it is definitely holding and using the last string.

2) The requirement that the version be changed with every upload. This is a real inconvenience, particularly since the site mishandles the string entered, and because this string does not appear anywhere else in the upload or download process that I've found, so what is the purpose in having a rule that this string be new and unique ?????

Since I have to deal with this every time I upload a new version for testing through download to the watch, I'm hoping that someone at Garmin will take an interest and fix the issue. Removing all restrictions on this field, or even the requirement to enter it would be a great start.

Jeff