-
Notifications
You must be signed in to change notification settings - Fork 149
Inability to work with cloud using OwnCloudBasicCredentials only (not android.accounts.Account) #257
Comments
@Den-Rimus please check master. Here you can find an overview of the branches: For stable, maybe check the releases: |
@davigonz update docs/README about stable? |
Same. It cannot work. |
Let me have a look... |
@Den-Rimus Yes, I can reproduce what you say and it should be fixed, this library suffered significant changes when we switched to a new network library so it's normal that this kind of things appear, thanks for reporting it. @michaelstingl since ownCloudClient and ownCloudAccount are much related with authentication and that's the next topic in terms of new architecture, I would address this issue there, what do you think? |
👍 |
Any news on this issue? it fails on me. |
Hi @lawer, can you still reproduce this? Let us know, please! 👍 |
When executing operations (e.g.
ReadRemoteFolderOperation
) - logic always ends up attempting to usemAccount.getSavedAccount()
inside client, which is alwaysnull
forOwnCloudAccount
instance if constructorpublic OwnCloudAccount(Uri baseUri, OwnCloudCredentials credentials)
used for creation.Is it even possible to work with plain username&password pair?
P. S.: is this even actual library to attempt to use for accessing ownCloud? It really looks like you gave up on implementing it in the middle of development and somehow gave it 'stable' status (at least I'm trying to use that branch).
Even your own sample app does not work (and it is, in fact, the only source of documentation for this library - every page related to Android client development redirects users to it).
The text was updated successfully, but these errors were encountered: