Skip to content

[Bug] Handling updated compatibility information of Patches #10

@Olf0

Description

@Olf0

Prelude:
When SFOS 2.1.0.11 was released, most Patches in Patchmanager's Web catalog were still marked as for "... 2.1.0.10 EA" at most, so I had to toggle "Enable developer mode" in order to install them. This worked nicely and these Patches are displayed in red in Patchmanager's installed Patches list (which is good).
Meanwhile all these Patches were refreshed and are now marked as compatible to 2.1.0.11 in the Web catalog, but their version numbers were not increased (most of them are at 0.0.2).
Bug description:
Consequently Patchmanager 2 obviously does not handle them as updated, hence still displayes them in red in Patchmanager's installed Patches list and still shows "Compatible: 2.0.1.10" in the detailed Patch information (by a tap on a Patch name) there.
Expected behaviour:
Updates of the "Compatible with" information in the Web catalog should trigger an update of this information for already installed Patches from the Web catalog, thus eventually not displaying them in red anymore.

Tested with Patchmanager 2.3.1-10.39.1.jolla on a Jolla 1 phone under SFOS 2.1.0.11

Originally reported on TMO as issue 1. (due to issue #9; filing this here as promised).

Metadata

Metadata

Assignees

No one assigned

    Labels

    UXdesign and behaviour of UI componentsenhancementthis improves something

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions