@davxuser said in DAVx5-ose (F-Droid) 3.0 doesn't start:
@rfc2822 Is 3.0-ose2 on google play store now? Thanks
No, in Google Play there’s 3.0-gplay. The versions -gplay, -ose and -standard have very minor differences (like the donation dialog and license info). -gplay (for distribution over Google Play) and -standard (for all other channels, like Amazon, Huawei and Samsung) are not affected.
The story behind everything: There is this small image (the background of the third image, these “dynamic ellipses”) we wanted to show below the DAVx5 logo on the intro screen. We found out that it’s not possible to buy a license for an open-source project, so we had to replace it with an empty image for the -ose version.
So I just removed the image data from the XML vector file in the -ose version, hoping that it would work and tagged the code as v3.0-ose. The F-Droid update bot soon noticed the new tag and updated the fdroiddata repo accordingly, taking 3.0 into the F-Droid repo.
Unfortunately, it crashes (of course), so I had to add a path which does nothing:
<path android:fillColor="#ffffffff" android:pathData="Z" /> Note that the Z command is only the end of a path, so the path doesn’t have any data, but it doesn’t crash now. I then tagged the code as v3.0-ose2, but F-Droid still didn’t detect the new version (29 Apr 22:46 CET).
So, all these problems and writings because it’s not possible to buy a license for a small background image on vectorstock.com for use in an open-source projects. Of course, I could/should have tested the -ose version before tagging, but usually I rely on the -gplay/-standard versions and the automated tests for -ose.
Part II: F-Droid detects version updated by tag names. Currently, the DAVx5 metadata file uses this regexp:
UpdateCheckMode: Tags ^v[0-9.]+-ose$ This means that -ose2 won’t be deteced automatically, so the new (fixed) version won’t make it into F-Droid automatically. Someone has already submitted a merge request, but the pipeline fails and it’s not merged yet…