Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Unable to sync repositories #719

Open
Merennor opened this issue Apr 20, 2024 · 10 comments
Open

[BUG] Unable to sync repositories #719

Merennor opened this issue Apr 20, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@Merennor
Copy link

Merennor commented Apr 20, 2024

Describe the bug
Repositories not synced with working WiFi (other apps working fine). Reinstalling doesn't help.
(Everything worked fine until March 2024)

To Reproduce
Steps to reproduce the behavior:

  1. Open app
  2. Click on 'Sync repositories'
  3. See error in Notifications

Expected behavior
Apps appear in the list of available apps (Explore)

Screenshots
image

Tablet:

  • Device: Huawei MediaPad M3 Lite
  • OS: Android 7.0
  • Version: v0.6.3

Additional context
Logs while syncing:
logcat.txt
The same thing in Neo Store BUT not in official F-Droid client.

@Merennor Merennor added the bug Something isn't working label Apr 20, 2024
@msinfo32github
Copy link

Having the same problem here running Android 14 (GrapheneOS) on a Pixel 7. Apps that have updates available seem to appear in the updates tab even though an error is presented however.

@Iamlooker
Copy link
Member

Can you try switching to a mirror of FDroid?

I am unable to reproduce this. And was this also the case in previous releases?

@Merennor
Copy link
Author

Merennor commented Apr 24, 2024

@Iamlooker on 0.5.1 everything was fine until March 2024. After - unknown error. BUT after updating to the latest version the same problem present.
Switching to this mirror fixed official F-Droid repo, but others like IzzyOnDroid still not working.

@Iamlooker
Copy link
Member

Can any one try and get logs? I am unable to reproduce this issue, and cannot help without logs

@msinfo32github
Copy link

This seems to have been fixed on my device by updating Droid-ify and then next time I checked for updates (multiple days later) it seems to have been fixed.

@lazy-pupp
Copy link

lazy-pupp commented Apr 24, 2024 via email

@okgamr
Copy link

okgamr commented May 18, 2024

I got this problem too
Screenshot_2024-05-18-21-19-38-726-edit_com.looker.droidify.jpg

But F-Droid repo syncs, aka no errors there

@tsssu
Copy link

tsssu commented May 30, 2024

I think this issue related to isp, some provider blocks izzy and fdroid repo and adding DoH support would fix this issue. The reason why is because i also facing the same problem here and connecting to WARP/1.1.1.1 seem to fix the issue which that's why im suggesting of adding DoH support.

@msinfo32github
Copy link

@tsssu Seems like you're correct in regards to an ISP issue - however I'm unsure if adding DoH will solve this? Are you using the 1.1.1.1 app? - I believe that's a VPN?

I've noticed recently this problem has been happening again for myself, and have noticed that navigating to some of the repositories itself has shown an error PR_END_OF_FILE_ERROR. I've been having some problems with my current ISP related to this error as well. However, on a second/third attempt on reloading the page it seems successful for every attempt after within a specified time period. (

I believe this is related to how my ISP uses CG-NAT (and not very well). It seems that maybe potentially adding a re-try by default (does this already exist?) or a configurable re-try in the settings could solve this problem for users with intermittent internet issues. - it seems like some users behind CG-NAT may have an IP address which changes often (e.g. every 30 seconds in worst cases) which causes this problem?

@tsssu
Copy link

tsssu commented Jun 2, 2024

@tsssu Seems like you're correct in regards to an ISP issue - however I'm unsure if adding DoH will solve this? Are you using the 1.1.1.1 app? - I believe that's a VPN?

Yeah, 1.1.1.1 app is using VPN service. I tried to use Private DNS feature on android and then switching between Adguard and cloudflare, but the problem no longer exists on my device even without enabling Private DNS. So i cannot making sure it would resolve this issues sorry, but i saw some app implemented DoH just in case if something wrong in some nations.

It seems that maybe potentially adding a re-try by default (does this already exist?) or a configurable re-try in the settings could solve this problem for users with intermittent internet issues.

I would agree to that if you want to plan adding re-try button in the notification because so far i dont think there is any.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants