Revision history [back]
 | 1 | initial version | posted 2017-05-25 09:26:50 +0200  |
Harbour detects app version as 2.1.0.*, but it works on 2.0.5
From the “OS version limits” drop-down at harbour.jolla.com, I can only select “---” or “2.1.0.*” when submitting an app, but I would like to select 2.0.5 so I can see an own app in Jolla store and install it from there instead of deploying the RPM through SailfishOS SDK. I'm running 2.0.5.6 (Haapajoki) (armv7hl) on my device.
If that OS version detector is right and the app is really only compatible from e. g. 2.0.5.4 but would fail on all devices between 2.0.5.0 and 2.0.5.3, how can I know which features caused the incompatibility, so that I could refactor them for broader backwards compatibility?
Best regards
Amica
| | 2 | retagged |
Harbour detects app version as 2.1.0.*, but it works on 2.0.5
From the “OS version limits” drop-down at harbour.jolla.com, I can only select “---” or “2.1.0.*” when submitting an app, but I would like to select 2.0.5 so I can see an own app in Jolla store and install it from there instead of deploying the RPM through SailfishOS SDK. I'm running 2.0.5.6 (Haapajoki) (armv7hl) on my device.
If that OS version detector is right and the app is really only compatible from e. g. 2.0.5.4 but would fail on all devices between 2.0.5.0 and 2.0.5.3, how can I know which features caused the incompatibility, so that I could refactor them for broader backwards compatibility?
Best regards
Amica