[BUG] Versions 1.4.0 and 1.5.0 not updated on F-Droid #648

skyegecko · 2020-03-03T09:50:43Z

F-Droid lists 1.3.3 as the latest version: https://f-droid.org/packages/com.zeapo.pwdstore/

It seems the build metadata is not up to date. I don't know if this file is maintained by this project, or whether someone from F-Droid keeps it up to date.

msfjarvis · 2020-03-03T09:56:22Z

AFAICT we're not the ones in charge of the F-Droid metadata. If someone wants to send them a PR with the new package name they're more than welcome to.

hlavki · 2020-03-24T15:20:31Z

Same on play store. Latest version is 1.3.2 from December 2018.

msfjarvis · 2020-03-24T15:49:16Z

Same on play store. Latest version is 1.3.2 from December 2018.

You're looking at the wrong listing then. The README has an updated link that takes you to the active version.

fmeum · 2020-03-27T14:05:28Z

I have "successfully" set up fdroidserver (https://gitlab.com/fdroid/fdroidserver/-/issues/756 should explain the quotes, it's been a bit of a wild ride) and built Password Store with it. Once I've become more familiar with the metadata language, we can submit a PR.

fmeum · 2020-03-27T14:37:39Z

The following config provides a working F-Droid build. Main findings:

We should ensure that for release tags tag name, version code and version name correspond to each other.
F-Droid's auto update feature cannot deal with the split between build.gradle and dependencies.gradle. So either that split has to go or we will have to submit F-Droid PRs from time to time.

Categories:
  - Internet
  - Science & Education
License: GPL-3.0-only
WebSite: https://github.com/android-password-store/Android-Password-Store/wiki
SourceCode: https://github.com/android-password-store/Android-Password-Store
IssueTracker: https://github.com/android-password-store/Android-Password-Store/issues
Translation: https://www.transifex.com/android-password-store/android-password-store/
Changelog: https://github.com/android-password-store/Android-Password-Store/releases

AutoName: Password Store
Description: |-
    Simple password manager that is compatible with [http://www.passwordstore.org/
    pass]: Passwords are stored in simple text files which are encrypted with
    OpenPGP.

    Requires [[org.sufficientlysecure.keychain]] to encrypt and decrypt passwords.

    '''Features:'''

    * Clone an existing pass repository
    * Initialize a new pass repository
    * List the passwords
    * Handle the directories as categories
    * Decrypt the password files (first line is the password, the rest is extra data)
    * Add a new password to the current category (or no category if added at the root)
    * Pull and Push changes to the remote repository
    * Ability to change remote repository info

RepoType: git
Repo: https://github.com/android-password-store/Android-Password-Store

Builds:
  - versionName: 1.7.0-SNAPSHOT
    versionCode: 10601
    commit: v1.6.0
    subdir: app
    gradle:
      - yes
    scandelete:
      - app/src/androidTest/assets/private_key

msfjarvis · 2020-03-27T15:00:03Z

The following config provides a working F-Droid build. Main findings:

We should ensure that for release tags tag name, version code and version name correspond to each other.

F-Droid's auto update feature cannot deal with the split between build.gradle and dependencies.gradle. So either that split has to go or we will have to submit F-Droid PRs from time to time.

We ran into this problem at WireGuard as well and our solution was to resort to directly fetching latest releases using the HTTPS method. Try going through the commit history for metadata to how the com.wireguard.android package is tracking updates.

fmeum · 2020-03-27T16:35:34Z

Try going through the commit history for metadata to how the com.wireguard.android package is tracking updates.

Thanks for the suggestion, this seems like it could work. But there are two more issues:

Afaik GitHub does not offer a URL under which the version of a file in the latest tag can be obtained. We would thus have to keep a file in the repo which is updated once a release comes out or published as a release artifact.
According to https://f-droid.org/en/docs/Update_Processing/, the automatic updates do not automatically add Builds directives to the metadata. So it seems that automated updates still require manual PRs, and I don't really understand what the point of AutoUpdateMode is if that is actually true.

msfjarvis · 2020-03-27T16:42:58Z

Try going through the commit history for metadata to how the com.wireguard.android package is tracking updates.

Thanks for the suggestion, this seems like it could work. But there are two more issues:

Afaik GitHub does not offer a URL under which the version of a file in the latest tag can be obtained. We would thus have to keep a file in the repo which is updated once a release comes out or published as a release artifact.

Can we not simply fetch the latest tag from the API?

According to https://f-droid.org/en/docs/Update_Processing/, the automatic updates do not automatically add Builds directives to the metadata. So it seems that automated updates still require manual PRs, and I don't really understand what the point of AutoUpdateMode is if that is actually true.

I don't understand F-Droid at all...

fmeum · 2020-03-27T16:51:33Z

Can we not simply fetch the latest tag from the API?

We can use something like https://api.github.com/repos/android-password-store/Android-Password-Store/releases/latest to get info about the latest release, but F-Droid only allows us to supply two regexes that extract the version name and code out of that. Parsing the version name out of the API response is easy, getting the version code would probably require major trickery (or putting it in the release notes, which are part of the API response).

I don't understand F-Droid at all...

I will give up on this for now, as I don't understand it either. I will revisit this in time for the 1.7.0 release.

msfjarvis · 2020-04-13T22:27:44Z

@FabianHenneke would moving version back into app/build.gradle help? I don't wish for anybody to spend too much time mucking around F-Droid so if we can fix it on our end let's just do that instead.

fmeum · 2020-04-14T09:00:33Z

@FabianHenneke would moving version back into app/build.gradle help? I don't wish for anybody to spend too much time mucking around F-Droid so if we can fix it on our end let's just do that instead.

Yes, this would help to some extent, but we would also need to keep versionCode, versionName and tag consistent on future releases. For the https://github.com/android-password-store/Android-Password-Store/blob/v1.6.0 tag, they are unfortunately all different. But I can manually add that release and we do this right for v1.7.0.

msfjarvis · 2020-04-14T09:04:44Z

@FabianHenneke would moving version back into app/build.gradle help? I don't wish for anybody to spend too much time mucking around F-Droid so if we can fix it on our end let's just do that instead.

Yes, this would help to some extent, but we would also need to keep versionCode, versionName and tag consistent on future releases. For the v1.6.0 tag, they are unfortunately all different. But I can manually add that release and we do this right for v1.7.0.

What would the right thing be here? I do believe this is correct. I can start taking care to tag the stable version bump rather than the snapshot bump if that's the problem.

fmeum · 2020-04-14T09:08:09Z

What would the right thing be here? I do believe this is correct. I can start taking care to tag the stable version bump rather than the snapshot bump if that's the problem.

Yes, that is the commit that should have been tagged. It's not a big deal though, I can simply add this version manually.

That said, what should I do with the old Password Store listing? I can either delete it entirely (not sure whether this is against fdroid policy though) or rename it to "Password Store (legacy)"?

msfjarvis · 2020-04-14T09:14:58Z

What would the right thing be here? I do believe this is correct. I can start taking care to tag the stable version bump rather than the snapshot bump if that's the problem.

Yes, that is the commit that should have been tagged. It's not a big deal though, I can simply add this version manually.

Thanks, I'll rework my scripts.

That said, what should I do with the old Password Store listing? I can either delete it entirely (not sure whether this is against fdroid policy though) or rename it to "Password Store (legacy)"?

I think we should just rename. Deleting outright seems unnecessary.

fmeum · 2020-04-14T10:05:28Z

I have drafted a PR that we could submit once v1.7.0 is out: f-droid/fdroiddata@master...FabianHenneke:fhenneke_aps

Apart from updating the donation link, I have made some changes to the description. Let me know what you think @msfjarvis @Skrilltrax @zidhuss

msfjarvis · 2020-04-14T10:08:03Z

I have drafted a PR that we could submit once v1.7.0 is out: f-droid/fdroiddata@master...FabianHenneke:fhenneke_aps

Apart from updating the donation link, I have made some changes to the description. Let me know what you think @msfjarvis @Skrilltrax @zidhuss

LGTM 👍

jvanbruegge · 2020-04-15T10:26:44Z

Not sure if this is still relevant, but I recently found out that there is indeed a way to get a link to the latest release. I use it here to download a precompiled binary in a github action

fmeum · 2020-04-15T15:53:11Z

Not sure if this is still relevant, but I recently found out that there is indeed a way to get a link to the latest release. I use it here to download a precompiled binary in a github action

Thanks for bringing this up. Unfortunately this seems to apply only to files specifically added to a release and thus would also require extra setup to generate.

ulfi · 2020-04-16T18:51:58Z

Uppss...
created an issue at f-droid about old version:
https://gitlab.com/fdroid/fdroiddata/-/issues/2015

fmeum · 2020-04-22T09:19:22Z

I just verified that moving the application ID back into build.gradle does indeed make fdroid checkupdates find the most recent version based on tags. I have the PR ready to submit for the v1.7.1 release.

fmeum · 2020-04-22T09:37:19Z

Nevermind, build is still broken since https://maven.mozilla.org/maven2 is not a whitelisted Maven repository. Will submit a PR.

msfjarvis · 2020-05-12T09:19:40Z

When v1.8.0 rolls around we'll hopefully now be able to get F-Droid builds out as well.

fmeum · 2020-05-12T09:28:13Z

When v1.8.0 rolls around we'll hopefully now be able to get F-Droid builds out as well.

I have updated my fdroiddata PR: https://gitlab.com/fabian.henneke/fdroiddata/-/commit/ca8039def0ac126832649a62919c6a19eff0d85f
Once we are happy with it, I would simply run checkupdates and check whether we can even enable reproducible builds.

msfjarvis · 2020-05-12T09:55:26Z

When v1.8.0 rolls around we'll hopefully now be able to get F-Droid builds out as well.

I have updated my fdroiddata PR: https://gitlab.com/fabian.henneke/fdroiddata/-/commit/ca8039def0ac126832649a62919c6a19eff0d85f
Once we are happy with it, I would simply run checkupdates and check whether we can even enable reproducible builds.

This looks good to go

fmeum · 2020-05-14T05:57:54Z

Are we interested in using Fastlane/Triple-T? They seem to be compatible with F-Droid: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/6775#note_342115325

msfjarvis · 2020-05-14T06:51:49Z

Are we interested in using Fastlane/Triple-T? They seem to be compatible with F-Droid: gitlab.com/fdroid/fdroiddata/-/merge_requests/6775#note_342115325

I wanted to look into using Fastlane and even without it I'll take anything to avoid more interaction with F-Droid than absolutely necessary. Please add the metadata to our repository.

fmeum · 2020-05-23T15:16:53Z

In order to get 1.8.0 to build on F-Droid, I will have to add a scanignore for the binary version of the Public Suffix List, but that should be fine.

Out of curiosity, I also enabled binary verification and ended up with the following diff between our release and the F-Droid build:

DEBUG: > diff -r
/tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800
DEBUG: removing unsigned/dev.msfjarvis.aps_10800.apk
DEBUG: removing unsigned/binaries/dev.msfjarvis.aps_10800.binary.apk
ERROR: Could not build app dev.msfjarvis.aps: compared built binary to
supplied reference binary but failed
==== detail begin ====
Unexpected diff output:
diff -r /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/apktool/apktool.yml
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/apktool/apktool.yml
2c2
< apkFileName: dev.msfjarvis.aps_10800.binary.apk
---
> apkFileName: sigcp_dev.msfjarvis.aps_10800.apk
diff -r /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/apktool/smali/$$ServiceLoaderMethods.smali
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/apktool/smali/$$ServiceLoaderMethods.smali
13c13
<     new-array v0, v0, [Lkotlinx/coroutines/CoroutineExceptionHandler;
---
>     new-array v0, v0, [Lkotlinx/coroutines/android/AndroidDispatcherFactory;
17c17
<     new-instance v2, Lkotlinx/coroutines/android/AndroidExceptionPreHandler;
---
>     new-instance v2, Lkotlinx/coroutines/android/AndroidDispatcherFactory;
19c19
<     invoke-direct {v2},
Lkotlinx/coroutines/android/AndroidExceptionPreHandler;-><init>()V
---
>     invoke-direct {v2}, Lkotlinx/coroutines/android/AndroidDispatcherFactory;-><init>()V
55c55
<     new-array v0, v0, [Lkotlinx/coroutines/android/AndroidDispatcherFactory;
---
>     new-array v0, v0, [Lkotlinx/coroutines/CoroutineExceptionHandler;
59c59
<     new-instance v2, Lkotlinx/coroutines/android/AndroidDispatcherFactory;
---
>     new-instance v2, Lkotlinx/coroutines/android/AndroidExceptionPreHandler;
61c61
<     invoke-direct {v2},
Lkotlinx/coroutines/android/AndroidDispatcherFactory;-><init>()V
---
>     invoke-direct {v2}, Lkotlinx/coroutines/android/AndroidExceptionPreHandler;-><init>()V
diff -r /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/apktool/smali/kotlinx/coroutines/CoroutineExceptionHandlerImplKt.smali
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/apktool/smali/kotlinx/coroutines/CoroutineExceptionHandlerImplKt.smali
23c23
<     invoke-static {}, L$$ServiceLoaderMethods;->$load1()Ljava/util/Iterator;
---
>     invoke-static {}, L$$ServiceLoaderMethods;->$load2()Ljava/util/Iterator;
diff -r /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/apktool/smali/kotlinx/coroutines/internal/MainDispatcherLoader.smali
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/apktool/smali/kotlinx/coroutines/internal/MainDispatcherLoader.smali
45c45
<     invoke-static {}, L$$ServiceLoaderMethods;->$load2()Ljava/util/Iterator;
---
>     invoke-static {}, L$$ServiceLoaderMethods;->$load1()Ljava/util/Iterator;
Binary files /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/content/classes.dex
and /tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/content/classes.dex
differ
==== detail end ====
INFO: Finished
INFO: 1 build failed

Everything here seems related to coroutines, but since all Kotlin language/stdlib versions are tracked in build.gradle, I don't know what to do about these diffs. Any ideas on what might cause this?

msfjarvis · 2020-05-23T15:54:44Z

In order to get 1.8.0 to build on F-Droid, I will have to add a scanignore for the binary version of the Public Suffix List, but that should be fine.

Out of curiosity, I also enabled binary verification and ended up with the following diff between our release and the F-Droid build:

DEBUG: > diff -r
/tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800
DEBUG: removing unsigned/dev.msfjarvis.aps_10800.apk
DEBUG: removing unsigned/binaries/dev.msfjarvis.aps_10800.binary.apk
ERROR: Could not build app dev.msfjarvis.aps: compared built binary to
supplied reference binary but failed
==== detail begin ====
Unexpected diff output:
diff -r /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/apktool/apktool.yml
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/apktool/apktool.yml
2c2
< apkFileName: dev.msfjarvis.aps_10800.binary.apk
---
> apkFileName: sigcp_dev.msfjarvis.aps_10800.apk
diff -r /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/apktool/smali/$$ServiceLoaderMethods.smali
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/apktool/smali/$$ServiceLoaderMethods.smali
13c13
<     new-array v0, v0, [Lkotlinx/coroutines/CoroutineExceptionHandler;
---
>     new-array v0, v0, [Lkotlinx/coroutines/android/AndroidDispatcherFactory;
17c17
<     new-instance v2, Lkotlinx/coroutines/android/AndroidExceptionPreHandler;
---
>     new-instance v2, Lkotlinx/coroutines/android/AndroidDispatcherFactory;
19c19
<     invoke-direct {v2},
Lkotlinx/coroutines/android/AndroidExceptionPreHandler;-><init>()V
---
>     invoke-direct {v2}, Lkotlinx/coroutines/android/AndroidDispatcherFactory;-><init>()V
55c55
<     new-array v0, v0, [Lkotlinx/coroutines/android/AndroidDispatcherFactory;
---
>     new-array v0, v0, [Lkotlinx/coroutines/CoroutineExceptionHandler;
59c59
<     new-instance v2, Lkotlinx/coroutines/android/AndroidDispatcherFactory;
---
>     new-instance v2, Lkotlinx/coroutines/android/AndroidExceptionPreHandler;
61c61
<     invoke-direct {v2},
Lkotlinx/coroutines/android/AndroidDispatcherFactory;-><init>()V
---
>     invoke-direct {v2}, Lkotlinx/coroutines/android/AndroidExceptionPreHandler;-><init>()V
diff -r /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/apktool/smali/kotlinx/coroutines/CoroutineExceptionHandlerImplKt.smali
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/apktool/smali/kotlinx/coroutines/CoroutineExceptionHandlerImplKt.smali
23c23
<     invoke-static {}, L$$ServiceLoaderMethods;->$load1()Ljava/util/Iterator;
---
>     invoke-static {}, L$$ServiceLoaderMethods;->$load2()Ljava/util/Iterator;
diff -r /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/apktool/smali/kotlinx/coroutines/internal/MainDispatcherLoader.smali
/tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/apktool/smali/kotlinx/coroutines/internal/MainDispatcherLoader.smali
45c45
<     invoke-static {}, L$$ServiceLoaderMethods;->$load2()Ljava/util/Iterator;
---
>     invoke-static {}, L$$ServiceLoaderMethods;->$load1()Ljava/util/Iterator;
Binary files /tmp/tmpie50lykq/unsigned_binaries_dev.msfjarvis.aps_10800.binary/content/classes.dex
and /tmp/tmpie50lykq/_tmp_tmpie50lykq_sigcp_dev.msfjarvis.aps_10800/content/classes.dex
differ
==== detail end ====
INFO: Finished
INFO: 1 build failed

Everything here seems related to coroutines, but since all Kotlin language/stdlib versions are tracked in build.gradle, I don't know what to do about these diffs. Any ideas on what might cause this?

Not really sure why that would be...

➜  gradle androidDependencies | grep coroutines | grep -v 1.3.5
➜

Even our transitive dependencies are all using coroutines 1.3.5

fmeum · 2020-05-23T16:02:46Z

Could it have something to do with R8? I vaguely recall some coroutine dispatcher related optimizations in R8. I'm not sure how R8 is versioned though.

msfjarvis · 2020-05-23T16:04:37Z

Could it have something to do with R8? I vaguely recall some coroutine dispatcher related optimizations in R8. I'm not sure how R8 is versioned though.

R8 is versioned by the Android Gradle Plugin, it's pinned to a specific version and cannot be overriden by transitive dependencies.

fmeum · 2020-05-23T17:27:53Z

I updated the MR at https://gitlab.com/fdroid/fdroiddata/-/merge_requests/6775. Should not be much longer until we are on F-Droid again.

msfjarvis · 2020-06-16T22:39:49Z

Don't think we'll be able to get on F-Droid in time for this month's release either, our MRs are just going stale over on F-Droid GitLab :/

Kaned1as · 2020-06-17T15:14:35Z

I have 2 such MRs myself. Waiting in line. But I don't mind. Thanks for pushing it this far.

msfjarvis · 2020-06-20T07:22:02Z

The new listing with dev.msfjarvis.aps package name should show up on F-Droid soon depending on when their backlog gets processed, we're still in the middle of having the previous listing deprecated. Thanks to @FabianHenneke for keeping at this!

https://gitlab.com/fdroid/fdroiddata/-/merge_requests/6844

msfjarvis · 2020-06-22T06:59:56Z

v1.8.1 has been deployed to F-Droid, v1.9.0 shouldn't be too far behind: https://f-droid.org/packages/dev.msfjarvis.aps/

fmeum · 2020-06-22T07:12:04Z

v1.8.1 has been deployed to F-Droid, v1.9.0 shouldn't be too far behind: https://f-droid.org/packages/dev.msfjarvis.aps/

Do we know why the Markdown links are not shown correctly?

What I also don't know: Are there any manual steps involved in getting this updated to v1.9.0? I guess we'll know in a few days though.

msfjarvis · 2020-06-22T07:14:17Z

v1.8.1 has been deployed to F-Droid, v1.9.0 shouldn't be too far behind: f-droid.org/packages/dev.msfjarvis.aps

Do we know why the Markdown links are not shown correctly?

Hopefully a problem on their end.

What I also don't know: Are there any manual steps involved in getting this updated to v1.9.0? I guess we'll know in a few days though.

Shouldn't be but yeah we'll know in a few days.

Fixes #648 Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>

fmeum · 2020-06-22T07:26:10Z

I asked the maintainers about the missing links. Also, we broke the build (see https://gitlab.com/fdroid/fdroiddata/-/merge_requests/6997), so that may be part of the issue.

msfjarvis · 2020-06-22T07:27:32Z

I asked the maintainers about the missing links. Also, we broke the build (see gitlab.com/fdroid/fdroiddata/-/merge_requests/6997), so that may be part of the issue.

~~welp, I'll send a fix over.~~ nevermind I thought that was an issue not an MR.

fmeum · 2020-06-22T08:45:39Z

The new version has already been picked up: https://gitlab.com/fdroid/fdroiddata/-/commit/cdf2fe025e6b7932575040455cdc4cf854c461bb

Due to the switch to CI builds, the new version is also compatible with F-Droid's reproducible builds. I have submitted an MR to get this added: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/6998

fmeum · 2020-06-30T19:08:15Z

The old listing is now archived and should vanish from the F-Droid repo soon: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/7028

fmeum self-assigned this Mar 27, 2020

fmeum added this to the v1.7.0 milestone Mar 27, 2020

fmeum added 👷‍♂️ in progress labels Mar 27, 2020

msfjarvis mentioned this issue Apr 16, 2020

[BUG] Save not working after Android 10 update #714

Closed

fmeum modified the milestones: v1.7.0, v1.7.1 Apr 22, 2020

fmeum removed 🆘 help wanted labels Apr 22, 2020

fmeum closed this as completed in #762 May 12, 2020

msfjarvis removed the 🛑 blocked label May 12, 2020

msfjarvis added this to the v1.8.0 milestone May 12, 2020

fmeum reopened this May 12, 2020

fmeum added the ✔️ ready label May 12, 2020

msfjarvis removed this from the v1.8.0 milestone May 24, 2020

msfjarvis mentioned this issue Jun 22, 2020

README: re-add F-Droid #870

Merged

5 tasks

fmeum closed this as completed in #870 Jun 22, 2020

fmeum pushed a commit that referenced this issue Jun 22, 2020

README: re-add F-Droid (#870)

f8390ef

Fixes #648 Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>

ghost mentioned this issue Oct 6, 2020

Autofill subdomain logic matches every domain with a common TLD country code Kunzisoft/KeePassDX#728

Closed

[BUG] Versions 1.4.0 and 1.5.0 not updated on F-Droid #648

[BUG] Versions 1.4.0 and 1.5.0 not updated on F-Droid #648

Comments

skyegecko commented Mar 3, 2020

msfjarvis commented Mar 3, 2020

hlavki commented Mar 24, 2020

msfjarvis commented Mar 24, 2020

fmeum commented Mar 27, 2020

fmeum commented Mar 27, 2020

msfjarvis commented Mar 27, 2020 • edited Loading

fmeum commented Mar 27, 2020

msfjarvis commented Mar 27, 2020

fmeum commented Mar 27, 2020

msfjarvis commented Apr 13, 2020

fmeum commented Apr 14, 2020

msfjarvis commented Apr 14, 2020

fmeum commented Apr 14, 2020

msfjarvis commented Apr 14, 2020

fmeum commented Apr 14, 2020

msfjarvis commented Apr 14, 2020

jvanbruegge commented Apr 15, 2020

fmeum commented Apr 15, 2020

ulfi commented Apr 16, 2020

fmeum commented Apr 22, 2020

fmeum commented Apr 22, 2020

msfjarvis commented May 12, 2020

fmeum commented May 12, 2020

msfjarvis commented May 12, 2020

fmeum commented May 14, 2020

msfjarvis commented May 14, 2020

fmeum commented May 23, 2020 • edited Loading

msfjarvis commented May 23, 2020

fmeum commented May 23, 2020

msfjarvis commented May 23, 2020

fmeum commented May 23, 2020

msfjarvis commented Jun 16, 2020 • edited Loading

Kaned1as commented Jun 17, 2020

msfjarvis commented Jun 20, 2020

msfjarvis commented Jun 22, 2020

fmeum commented Jun 22, 2020

msfjarvis commented Jun 22, 2020

fmeum commented Jun 22, 2020

msfjarvis commented Jun 22, 2020 • edited Loading

fmeum commented Jun 22, 2020

fmeum commented Jun 30, 2020

msfjarvis commented Mar 27, 2020 •

edited

Loading

fmeum commented May 23, 2020 •

edited

Loading

msfjarvis commented Jun 16, 2020 •

edited

Loading

msfjarvis commented Jun 22, 2020 •

edited

Loading