You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 22, 2018. It is now read-only.
Visually separate upgrading to and downgrading from higher versioned packages
Example: User installed Telegram Beta (2.5.0.0), while OpenStore still has an earlier (stable) version installed.
Current behavior: Store detects different version number available, suggests upgrade — only closer examination below reveals that the newer version is already installed.
The text was updated successfully, but these errors were encountered:
There is a patch currently in progress for this use case.
What we planned to do is to list non-OpenStore apps in a separate section than “Available updates”; that would allow us to add a short explanation about the status of sideloaded/devel apps.
We came up with this solution with telegram-app in mind. Since the devel version of telegram-app might have some regression due to the bad status of Telegram APIs, We want to make easier for our users to find out sideloaded apps in OpenStore, and allow them to switch back to ‘stable’ if they wish so. Sideloaded apps wouldn’t be counted as pending updates in the bottom badge anymore.
Please let me know if this would solve your issue, we’re open to discuss any alternative solution.
Thanks again! :)
As this is a rather aesthetic feature suggestion, there is nothing really to resolve. I do not have enough insight to judge whether this is the best solution, but I'll say that even with this change I would still make the button at least say something different for installing over newer or older versions.
Visually separate upgrading to and downgrading from higher versioned packages
Example: User installed Telegram Beta (2.5.0.0), while OpenStore still has an earlier (stable) version installed.
Current behavior: Store detects different version number available, suggests upgrade — only closer examination below reveals that the newer version is already installed.
The text was updated successfully, but these errors were encountered: