-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to check whether a new version is available #79
Comments
Work is ongoing and a MVP is already working with manual version check. Still have to save last check timestamp in model and application state, and automatize the check. But working on this I feel that all that stuff is irrelevant to a weather application and should move to a 3rd party application with version check, signature check, unzip and install... In two words, an application store! |
Users interested in pre-relesaes can set |
The "check for new version" is implemented. Let's take some time to think of the "download, verify and update software" part. |
This app has a download mechanism: http://komary.net/pbdownload/ |
Thank you, @neilswann80. Nice example of the use of the SDK functions to perform and track downloads. It's definitively the path to follow: Provide an application dedicated to version check, download, verify and install. Unfortunately, it:
The third step is difficult and require playing with OpenSSL or GnuPG. |
Interesting investigations on the ".pbi" format: https://www.mobileread.com/forums/showpost.php?p=4385836&postcount=1 |
FYI I use the following update script on my device to update my version of Taranis when a new version becomes available,
Could this be streamlined into Taranis? |
Do you reboot after that? My experience is that there's a kind of cache and replacing the executable then restarting through an icon click isn't enough to start the new executable... Side remark. Reading your commment, I realized that the '.app' file could be attached to the release. Unzipping would then be unnecessary. Missing '.app' file from the release would tell that a manual install is required. Interesting. But I'd still prefer to download the '.pbi' to be able to perform a full install. Then back to my rengaine: This is the work of a dedicated application, not Taranis. Since I made no progress on the gargoyle port, I am worrying whether I should work on that application... Last remark, I've found that downloading the installer manually, copying to the device, etc. is so boring... I even didn't installed last minor release on my device. Improvment required! |
I don't need to reboot. I don't run the script with Taranis open, if that is what is causing your issue? Although a killall command could be added to close Taranis and then relaunch it after the update. Is it a symptom of USB transfer? I usually send files to my device via FTP, or direct downloads on the device and never experience a cached old file issue. If you've done the initial install via .pbi... do you really need to run a .pbi for every update? |
No I don't think my problem comes from the application being running. I guess it comes from the application having run before in the same boot. I must do some tests. |
I launched the old version of Tananis, ran my script, launched the new version of Taranis all within the same |
Proposal
Remarks
The text was updated successfully, but these errors were encountered: