-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Nextcloud files app (dev) from fdroid not recognised #78
Comments
Thank you for the report. We are currently talking to the authors of the Single-Sign-On about how this issue can be fixed. :) |
As far as I know SSO currently requires the official app installed, and cannot be used with dev version of files app. |
Thank you for the response!
OK, so it is a "problem" with the main app? Thank you! |
I've got something similar... With the normal Nextcloud Files app from F-Droid, when I open Deck, it shows a prompt to select the the account from the files app or "add an account"... When selecting my account (default) and clicking ok Deck shows an error with "you have to allow access to single-sign-on", however there was no promt or anything... |
For reference: nextcloud/Android-SingleSignOn#63 |
Hi @lachmanfrantisek, @violoncelloCH, Feel free to test the latest master (i bumped the version) and if it works, get those guys a beer already! 😁 |
The latest version of this app (0.0.5) supports the dev app of files. Please wait a few days until it gets released on F-Droid or compile it from the master branch. |
Describe the bug
The app (fdroid 0.0.2) shows the pop-up, that the Nextcloud files app is not installed. I am already using dev version of files app from the fdroid (20190502 version).
To Reproduce
Steps to reproduce the behavior:
... Account.getId()
on a null object reference.` (Should I need to create a new issue for this one?)Expected behavior
Screenshots
(Sorry for the czech version.)
Smartphone (please complete the following information):
Stacktrace
Thanks for your work! Looking forward to using it!
The text was updated successfully, but these errors were encountered: