Closed nicofrand closed 8 years ago
Thanks for reporting!
It happens even after uninstalling/installing the app again.
It appears to be the case for every app which git branch is different from master.
Yes, it's something we want. Because when you install a non master branch, it means you are in dev mode and that you expect to be able to update the app even when no new version is published.
Fine, I close the issue then !
Well, I'm not really comfortable with this choice. For example, for the port of Tablero, I work on a Cozy branch, for code specific to Cozy integration. So the default repo for this application will probably never be master, and users will never know if updates are really available.
That's the case for Shout too, and any porting I guess.
Besides, if I am in "dev mode" I can still force the update through cozy-monitor update app
, right ?
In the status page, there is an "update" button ofr the application Shout whereas the application is already uptodate (0.51.1 and I also tried with
cozy-monitor update shout
to be sure).My logs: