Add workaround for known issue in FAQ.md #660
Comments
|
Hi @HelplessFool thanks for your report, great nick btw! 😆 What version of the nextcloud files app have you running on the failing device? Maybe all you need to do is update it? |
|
Oh wait! It's THAT exception?!?! I summon the experts @stefan-niedermann, @David-Development and @tobiasKaminsky! Do your thing! |
|
Ok, @stefan-niedermann told me, that clearing the storage of both apps would help: https://github.com/stefan-niedermann/nextcloud-deck/blob/master/FAQ.md#i-have-experienced-an-error Please try to follow the steps described there. If even that won't help, please try to deactivate the battery saving options for the files app. Note: you will need to re-login to your account in the files app first after that. Hope this helps! |
|
Tried all that before reporting the problem. Also, tried creating a test account. Login, fine, try and use deck, fails with the same error. |
|
Did you get the files app from F-Droid, too or is it self-built? |
|
Everything is from F-Droid. As far as I can tell, everything is up to date as far as F-Droid is concerned. Hope that helps, as least to eliminate some problems. |
|
Yesterday another user had a problem with his F-Droid setup, see here: #662 (comment) Maybe there is something similar going on with your Files-app?
Sorry that we can't provide an exact solution for this, it's one of the weirdest and most random errors we face within our app. It only happens sometimes and no one can tell what is the root cause for this. Due to fragmentation in Android we have quite a hard time to resolve this issue once and for all, sorry for the inconveniences! EDIT:
We try to request the server version, but the exception above happens, so we display the minimum supported version as a fallback instead, no need to wonder. Your server version is fine here, no worries. We don't even get to the point, where the server version matters, because the requests to the server can't be sent at this point in cause of the error, anyways. |
|
Nice idea. Tried all that. Same error. Is there anything I can check on the server? Logs etc? I've got full access to it. |
|
Wow, that's pretty frustrating...
The server is fine, you won't see any logs there, because the requests made by the app never reach the server... this is an all Android-problem. At this point I'm out, no idea what to do. But our friends @tobiasKaminsky and @David-Development still might have some hints? They wrote the SSO-library which is throwing this error, maybe they know some things you could look up... |
|
@HelplessFool As you have tried all of our "failsave" solutions I'm a little clueless as well. Were you able to get the setup working on this particular device before? Or has the problem been there from the beginning? And you said your other two devices are running just fine, right? Can you give us some more information about the device? It's a Lenovo Tablet, right? Are you using a custom ROM? Or are you on the stock Android Version? |
|
Brief answers:
I'm just wondering what debugging I could do, either on the server or on the device. Would trying the combination of Nextcloud-dev with Deck help or is that a blind alley? I'm currently using the standard version of Nextcloud from F-droid. Other information: I basically don't use Play Store, have a firewall (with both Nextcloud and Deck allowed) but it doesn't work with it turned off either. Only wifi on the device. |
stefan-niedermann
added
the
🔐 single-sign-on
|
@HelplessFool can you please install the "Nextcloud Notes" app on your server and on your phone and try to connect? This way we might able to detect whether the problem is in the Deck app itself or in the lib (or files app). |
|
Nice idea. I've installed notes on the server and on my phone (Deck works) and tablet (Deck doesn't work).
So, I'm guessing the issue is not directly with the Deck app, but somewhere nearer the main Nextcloud app or communication between them. |
|
It does indeed look like an issue with the communication between the single sign on library and the nextcloud app. If you have disabled all power saving features (if available) I'm kinda running out of ideas as well. It is really difficult to debug this problem deeper as you would need to build the app yourself (including the single-sign-on library) and try to debug it. However I'm not sure if this will bring any new insights since I guess the service that we connect to is just not binding correctly. I'm wondering if this is somehow connected to the custom rom that you are running.. 🤔 @HelplessFool Do you have more logcat output for us? (not just error output) |
|
@David-Development How would I find more logcat output? What I provided initially was the error message that you can copy from the app. I'm happy to provide if I know how to get at it. |
@David-Development According to this medium article not 🤷♂️ |
|
@HelplessFool you should be able to find the logs by using an app (for example https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=de_CH) or by connecting your tablet to your computer and by running the @stefan-niedermann that's good! 😅 |
|
@David-Development I've got adb working so will have a look. Is the best thing to do to try the app, have it fail and then plug in and use adb? Anything particular that I should look for to know whether I'm looking at useful stuff or just random goings on on the device? |
|
@HelplessFool Would be good if you close both apps (nextcloud files app and deck app) and then start "recording" the log. Then start the deck app and try to login. Make sure that no sensitive data is in the log before sending it to us 🙂 Thank you! |
|
I think this is it: Tell me if you need more context. |
I guess that's what we're looking for. Who or what the hell is TabletMasterService? |
|
See this, below the post there is a guide you could try regarding "memory usage" Edit: yeah... Link: https://forums.lenovo.com/t5/Lenovo-Android-based-Tablets-and/Tab-M10-background-apps-getting-killed-right-away/m-p/4554370 |
|
That sorts it!!!!! Thank you. I've been struggling with the memory usage stuff. I've done some further debugging so that the exact issue can be identified. The results are as follows:
Right. So, it wasn't anything to do with the app directly, but was that the Nextcloud app was being blocked. Is that enough info to update the FAQ? |
|
Absolutely! Thank you very much for the great research! Let's keep this issue open until i found some time to update our README.md and maybe @David-Development wants to add some kind of "known issues" section in the SSO README.md? |
stefan-niedermann
changed the title
This comment has been minimized.
This comment has been minimized.
|
Pull Request for updating the README.md of SSO: nextcloud/Android-SingleSignOn#258 |
On selecting account and allowing access the following error is received:
Deck works with two other devices running the same version of the app. I can see files on the cloud using the nextcloud app. No errors occur there.
What further information would help you debug this?
The text was updated successfully, but these errors were encountered: