How long do I have to wait for a BETA app to appear in Connect IQ Store?

Am I doing something wrong?

As I'm forced by Garmin to upload my app to the store to be able to test the settings, this is what I do:

1. I export my app
2. upload MyApp.iq file to the store as BETA
3. give it a different version id than the previous one (BTW the same I also dump in manifest.xml)
4. hit publish
5. then write a few words in the "What's new" section
6. hit the Submit button

Am I being naive if I assume that a few seconds after I upload a BETA app, the newly uploaded version should appear in my Connect IQ Android app?
And I do see the text changes within seconds. But I'm waiting for hours to see (if at all?) the version to change.

Is there another/better/faster way to test settings? (nothing works in simulator...)

Alan.raceQs over 3 years ago in reply to jim_m_58

jim_m_58 said:
It will probably at the every end of the activity list

Yes, I expected the app to appear in the Activity List, but it didn't.

And it remained as {appName}.prg in the /APPS folder after disconnecting and reconnecting to the PC's USB cable.

jim_m_58 over 3 years ago in reply to Alan.raceQs

What FW version is the user running? Make sure it's the current production FW or the latest beta FW

Brandon.ConnectIQ over 3 years ago in reply to Alan.raceQs

This will sound like a silly question, but figured it might be worth a shot - is your tester actually unzipping the file and loading the extracted PRG or just renaming the .zip to .prg before side-loading? I only ask because, as Jim has mentioned, if it's any app type aside from a watch face, the file would be moved to a hidden directory and encrypted, but the device it acting like it's not a valid PRG.

Alan.raceQs over 3 years ago in reply to Brandon.ConnectIQ

Brandon.ConnectIQ said:
is your tester actually unzipping the file and loading the extracted PRG

I can only be 98% sure of that, as he was remote, so we were working over Zoom, but he was not an experienced user, so was following my instructions, in which I was very clear for the need to unzip the file.

Still, this conversation indicates that the problem was not with my expectation that the process should have worked, but more likely something to do the way it was undertaken, which may remain a mystery.

My concern about the file format and the need to use Android File Transfer to side-load from a Mac to a music device appear to have ben unfounded.

Thanks

Brandon.ConnectIQ over 3 years ago in reply to Alan.raceQs

I wouldn't suspect the file format or the use of Android File Transfer, but it's worth noting just in case. Generally, a zip file is a zip file.

jim_m_58 over 3 years ago in reply to Brandon.ConnectIQ

First thing I'd check on is the Firmware Version on the watch. Seems to me this issue may have been on the FW that was instated on the initial devices And some people don't install updates..