Dear all,
We have moved the AutoUpdate executable files to the Maven Central Repository.
Our update.xml file looks correct (attached).
When the AutoUpdate is launched, it detects a new version available, but then it gives an error downloading the file, it tries 3 times and it fails, even if that location is reachable from that computer.
What can be the problem? How can we get more information about the error? In the log files only a generic "Error downloading update. Retrying (1/3)" is reported.
If it can help you, attached you can find the error dump, generated running the AutoUpdate from command line with the command: $ ./autoupdate-linux-x64.run --debugtrace output.txt
Many thanks,
Stefano
<installerInformation> <versionId>202009271512</versionId> <version>3.26.18</version> <platformFileList> <platformFile> <filename>collect-updater-2-3.26.18-windows.exe</filename> <platform>windows</platform> </platformFile> <platformFile> <filename>collect-updater-2-3.26.18-windows.exe</filename> <platform>windows-x64</platform> </platformFile> <platformFile> <filename>collect-updater-2-3.26.18-linux.run</filename> <platform>linux</platform> </platformFile> <platformFile> <filename>collect-updater-2-3.26.18-linux-x64.run</filename> <platform>linux-x64</platform> </platformFile> <platformFile> <filename>collect-updater-2-3.26.18-osx.dmg</filename> <platform>osx</platform> </platformFile> </platformFileList> <downloadLocationList> <downloadLocation> <url>https://repo1.maven.org/maven2/org/openforis/collect/collect-updater-2/3.26.18</url> </downloadLocation> </downloadLocationList></installerInformation>
Hi StefanoRicci,
Can you try to enable <enableSslSupport> in the autoupdate project?
<project>
...
<enableSslSupport>1</enableSslSupport>
...
</project>
Regards,
Michiel
Hi StefanoRicci,
Can you try to enable <enableSslSupport> in the autoupdate project?
<project>
...
<enableSslSupport>1</enableSslSupport>
...
</project>
Regards,
Michiel
Many thanks,
that fixed the issue!
I think it would be better to enable it by default (it should be the regular condition, updaters deployed through SSH) and specify in the documentation that if it's not needed, it can be disabled.
Thanks again,
Stefano
Hi StefanoRicci,
I'm glad to hear that solved the issue. We don't enable it by default to keep backwards compatibility.
Regards,
Michiel