404 error checking for updates - what is proper updates directory structure?

[Martin Koob]

When I check for updates in my standalone I get a 404 error when checking for updates.

The update.txt file is found but the update.txt files have the wrong paths for the updater files.  

Could you look at what I have done and see  what is wrong here?

In the GLX App Plugin the settings are

Upload settings- 'path to update folder'

The FTP account's path is effectively

mysite.com/download/autoupdate/MyApp/3_0

so  the 'Path to update folder' is blank

Global Base Auto Update URL:

https://www.mysite.com/download/autoupdate/MyApp/3_0/

Development Base Auto Update URL: [this is in use]

https://www.mysite.com/download/autoupdate/MyApp/3_0/

When I check the update.txt file using Safari

https://www.mysite.com/download/autoupdate/MyApp/3_0/development/update.txt

It downloads and shows the following directory structure

https://www.mysite.com/download/autoupdate/MyApp/3_0/development/updater.gz

https://www.mysite.com/download/autoupdate/MyApp/3_0/development/development/3.0.3d176/app_macos_package.gz

https://www.mysite.com/download/autoupdate/MyApp/3_0/development/update_dialog.gz

The actual directory listings are this.

https://www.mysite.com/download/autoupdate/MyApp/3_0/development/update.txt

https://www.mysite.com/download/autoupdate/MyApp/3_0/updater.gz 

https://www.mysite.com/download/autoupdate/MyApp/3_0/development/3.0.3d176/app_macos_package.gz

https://www.mysite.com/download/autoupdate/MyApp/3_0/update_dialog.gz

So there is an extra 'development' in the path in the update.txt resulting in incorrect paths.

What change do I have to make to get this to work?

Thanks

Martin

[Martin Koob]

Hi Trevor

Just want to let you know I got it working.  Just in case someone else runs into this I will explain what I did to resolve it.

I had at one point previously set the Development base Auto Update URL incorrectly to 

https://www.mysite.com/download/autoupdate/MyApp/3_0/development 

Then I had uploaded that update file. That was the file with the extra 'development' in the paths.

I had changed it in the GLX App Plugin and saved it. Somehow it was being retained in the stack or perhaps it was being cached.

I added a line of debugging code to the _DownloadUpdateComponentData handler of the glxApplicationFramework stack to show the URL being used in an answer dialog.

After I saved that stack then rebuilt the App and tested it my debug code reported the correct URL for the updater dialog and the updater dialog was shown.

So perhaps it was saving the application stack that way that did something. (I also clicked the unload application button before loading the application, I normally quit LiveCode after each build not saving it so the values are not saved but maybe they had been saved at one point.)

The odd thing was after I took the line of debugging code out and saved the application stack again and rebuilt it again, when I launched the new build and checked for updates my debugging code still answered with the URL.  It seemed the application stack had not actually been saved.

I went back and saved the application stack again rebuilt etc. and this time the removal of the debugging code worked.

So it seemed that saving the application stack does not always seem to take the first time.

Anyway whatever did to change things means it is working now.  

Martin

On Thursday, 24 April 2014 15:05:10 UTC-4, Martin Koob wrote:

When I check for updates in my standalone I get a 404 error when checking for updates.

The update.txt file is found but the update.txt files have the wrong paths for the updater files.