PasswdSafeSync keeps asking permission for phone's secondary Drive account
Brought to you by:
jeffharris
To reproduce:
Expected behaviour: PasswdSafeSync syncs password files from the phone's primary Drive account, leaves phone's secondary account in peace.
Actual behaviour: PasswdSafeSync syncs password files from the phone's primary Drive account, asks for permission to access the phone's secondary Drive account every time it starts up.
Anonymous
Can you do a screenshot of the notification? I get some Android notifications for my seconday account for Google apps, but I don't see PasswdSafe Sync in them.
Sorry for the delay, here are the screenshots.
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Hi, were you able to reproduce?
No. I removed Sync app permissions from both accounts and attempted to recreate the issue as described. I received the notification for the main account but nothing for the secondary account. This was on my Oreo tablet.
That's extremely odd: so far, this has been happening to me on two different pixel phones as well as a tablet running LineageOs.
Could the fact that the accounts are the same username on different domains have anything to do with it?
I wouldn't think the same user name would affect things as I use the full account name. If you could, open the sync app's About screen and click to send the log to me. That may help.
I've just started getting this on a Google Pixel phone; I'm on Sync version 3.5.0. It asked for permission for both of my Google accounts; I granted the one, but refused the other, and continue to get exactly the message screenshotted by Federico.
Here's what I see, log-wise:
The sync for the account that I did approve is failing, showing "Last failure: [timestamp for 2 minutes ago]" on the main screen. The "About" screen's "Send logs" button just produces an empty output... :-/
* Tapping the little "rewind clock" icon in the top bar shows a log, with the following message repeated for every sync attempt:
If you click on the error in the logs list, it should expand with a full trace. Please send me a screenshot of the error. Thanks.
Here's a stack trace from my phone!
Just an update, I've reproduced the issue. The fix, though, is a bit more complex as there was a change with how the system handles account access for syncs.
Amazing! Thank you for looking into it! I guess it happens to very few users, but when it does, it's very annoying!
Verified: version 3.5.1 no longer has this problem. Thank you!