-
-
Notifications
You must be signed in to change notification settings - Fork 258
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
Fails to update feeds - Nextcloud API not responding #769
Comments
@mirdaki Thanks for your feedback! It's weird that the first sync is working but all later ones fail. Just double checked and the exception Did you try restarting your phone? What version is the Nextcloud Files App on? |
The issue seems to persist across restarts. I'm using version 3.6.0 of the Nextcloud files app, also from F-Droid. I just tried signing in without using the single sign on and that seems to be working (no error messages, but I don't have any new items in my feed yet). |
@mirdaki Okay, thank you for the information! Am I understanding you correctly that the normal sync is not working either? Or you are just waiting for new feeds? I'm working on quite some changes as we speak and I might be able to release a first beta sometime soon. What theme are you using in the nextcloud news app? There might be some issues when using the dark-theme. (They will be fixed in the next release) |
I think I'm just waiting for new feed (I'm able to mark articles as read on the web interface and that is syncing with the Android version). Currently using the "Light / Dark (based on Daytime)" theme (it's currently light for me). |
Oh huh, so I switched back to the SSO from the regular sign on just to see and it seems to be properly syncing again (new feed appeared with no error). Previously I had signed out and back in though SSO and that did not fix the issue. |
@mirdaki awesome! Let me know if you encounter any issue again later on. I'll close this issue for now. Reopen if you encounter it again. |
Hey @David-Development the feed stopped updating earlier today (same error message) with SSO. I've switched back to regular sign on and haven't had an issue on that |
It seems there needs to refresh something in the SSO every now and then. It already occurred to me several time, the app fails to update giving me the same exception. Just turning SSO off and on solves the issue each time |
I can confirm what @marco44 said about refreshing SSO. I just had this error and after finding this thread, I went to Server Settings, disabled the SSO switch, then re-enabled it and selected the account. After that, the server sync worked again. |
The nextcloud notes app has a similar issue (Ref: nextcloud/notes-android#653). As a follow up question to investigate this issue a little more. Is everyone in this thread (@marco44 and @ThomasRitter75) using the fdroid version of both files and news app? |
I am using the f-droid version. |
I think I'm using the google play version. Not sure though, it's been a while I've installed it |
Using the F-Droid version as well, will be downgrading the app shortly as this error prevents any news synchronization (as well as this new version does not allow you to use the app if you deny the location permission - which I think is only required if you use the time-of-day theme rule). |
Should be fixed in 0.9.9.35. If not, please reopen |
I have now seen two occurences of "API not responding". Cleaning app data and setting up the account again fixed the problem.
@ThomasRitter75 How did you "disable SSO"? Where do I find this setting? |
When I go to update my feeds I get a toast with "com.nextcloud.android.sso.exceptions.NextcloudApiNotRespondingException: Nextcloud files app api not responding. Please report this issue". Existing feeds are unaffected. I can get it to fetch new feeds by signing out and back in, but it fails to sync afterwords.
I'm running Android 9 on a OnePlus 5, with Nextcloud News 0.9.9.25 from F-Droid. My Nexcloud system is using the snap package with version 15.0.7.
Let me know if there is any other information I can provide!
The text was updated successfully, but these errors were encountered: