bcutter
bcutter
Still happens on latest version (v4.2.0). Quite annoying, depending on the login duration. ANY ideas?
If you can assist me on how to prove this I certainly could. Maybe by just disabling suspicious_login app and trying to login? Expectation: - app enabled: 1st login attempt...
Still nothing from the UI (which should be fine for everyone having direct access to `datadir/ownbackup` folder).
Running it on NC 23. Doesn't work (no backups are created, even when ran manually).
So do we need to point someone from core/server to this as suspected latest update caused this issue?
Perfect! ✅ Background job support ❌ Jobs: returned nothing (empty set) ✅ After disabling and reenabling the app and waiting few minutes: job exists and number is being created So...
Ah come on guys... you ping pong users from one side to the other :-D Why don't you talk with each other to find a solution ;-) So here we...
That's a workaround. So let's look/wait for a _fix_.
Update: found https://github.com/custom-components/authenticated/issues/82 which has been closed - but the issue still persists. Did I miss something, what do I need to do to get the fix of #77 ?
Already thought about this. But that's not how things should work normally*, right? Even **because** it's only one line... I don't get why it takes weeks to ship a new...