Adding ownCloud account fails after timeout without notification
Brought to you by:
jeffharris
Menu
▾
▴
#35 Adding ownCloud account fails after timeout without notification
I tap the "+", tap "ownCloud", and tap my ownCloud account. It spins on "Adding account... Select notification within 60s to authorize access." for probably about 60s and then returns to the main app page. I can detect no notification to select.
Environment: Moto G5 Plus, Android 7.0, ownCloud app 2.4.0, PasswdSafe Sync 3.4.2.
Discussion
Anonymous
Support for ownCloud on some Android 7 versions is not possible due to a bug in Android itself. However, with the Oreo release, the bug appears to be fixed though the account may have to be added twice.
While I wait for Oreo to be available on my device, can you suggest a workaround so that I can continue to use PasswdSafe Sync with ownCloud?
If you have the ownCloud app itself, you should be able to at least open files from it. It seems to support saving as well, but I'd verify to make sure it works for you as well.
Any other workaround involves writing a whole new method to handle logins manually and not using the ownCloud accounts on your device.
Unfortunately this only works partially... The (actual) psafe3 file is not downloaded until you click it from the ownCloud app, which means that in an off-line situation there is no access to the current psafe3 file.
Can you be more specfic on the Android 7 bug? It may be a while until we get Oreo (if at all).
The android bug is described at https://issuetracker.google.com/issues/37127434.
Until you get Oreo, the best option is to just use the ownCloud app and not PasswdSafe Sync. You should be able to read and write (though test first) files opened from the ownCloud app.
Got Oreo, retrying.
Initially, I got many sync failures "network not connected" although the networking is fine, and ownCloud works okay. But this could be a residue from the pre-Oreo configuration.
So I removed the account from PSSync. When trying to use the existing ownCloud account it says there is none (note: there is). When trying to add a new account it says "Add an account in the ownCloud app first". However, this cannot be done since there is an account already.
So I added a new account for PSSsync (using Settings > Accounts), but it is rejected since "An account for the same user and server already exists".
I'm running a bit out of ideas...
Try reinstalling the whole Sync app. There may be some residue account access info in the device that a reinstall should clear. Or, try rebooting the device.
Reinstall/reboot doesn't make a difference. I added new ownCloud accounts
after reinstall, but PasswdSafe Sync keeps saying there are no ownCloud
accounts to use.
Note that in Settings > Apps, PasswdSafe Sync has permission set for
Contacts, but there is no permission for Accounts?
I'd just like to confirm the problem (on android 8.1.0); both passwd sync and owncloud have Contacts permission, but It is impossible to select (existing) ownCloud account because passwdSafe Sync claims there are no ownCLoud accounts, and that I should add one. Cheers, Sven
Currently I'm unable to test with ownCloud as it is broken on Fedora 28. Until there's an update to make it work, I would suggest using the official ownCloud app for your files. If you open a .psafe3 file, it should launch PasswdSafe, and I believe it will sync changes back to your account. Please test whether the updates are saved before making any important updates.
On Sat, 08 Sep 2018 17:50:34 -0000, noreply@sourceforge.net wrote:
According to the first posting in the thread this would be solved in Android 8.
Now I'm getting confused...
ownCloud was working on Android 8 last I tested. I can't confirm the above report about 8.1.0 as my ownCloud server is broken on the newest Fedora OS. If ownCloud's own app works, I would suggest using it currently.