-
Notifications
You must be signed in to change notification settings - Fork 34
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
Connected App shows 0 Passwords #259
Comments
I have the same Issue. My Nextcloud server was recently upgraded to NC 27 and passwords app is therefore using latest API (2023.08). I guess it could have something to do with that. Any other log or any information I can give to help, please ask. Thank you! Android App is working fine, though. EDIT: I found the place where the debug is:
Also, using Mozilla Firefox 115.0.3 |
The Problem dissapeared for me after about two days (i guess..). Everything is working now as expected. Still no clue why.. |
I was adding more information and just realized it has started to work...really weird! |
hello, edit: after disable and re enable the extension, it worked... |
Had the same issue on different maschines. Always fixing itself within a few days. |
Same issue after upgrading to NextCloud 28. Re-enabling or re-linking the extension did not work. Any solution? |
I guess "something" takes a while until it works...not sure what it is 🤷 |
System Information
Steps to reproduce
connect -> sync -> see no Passwords..
Expected result
Be able to access the Passwords.
Actual result
Information shows 0 Passwords on Server.
Addon worked fine and suddenly stopped showing Suggestions. I tried to remove and add the Account without resolving the Problem. Problem affects both Servers accesible to me (both have same App Version).
Wenn syncing debug shows:
{ "details": { "data": { "module": {}, "message": { "id": "241944d8-ba7f-499d-8c26-f585fba5a64e", "tab": null, "type": "server.reload", "reply": null, "silent": false, "sender": "popup", "channel": "runtime", "payload": "9fece5a2-fabe-4e96-82cb-f0c0ffa23ec8", "receiver": "background" }, "reply": { "id": "228141eb-30d3-4b8f-94a0-62df4e0a174f", "tab": null, "type": null, "reply": "241944d8-ba7f-499d-8c26-f585fba5a64e", "silent": false, "sender": "background", "channel": "runtime", "payload": null, "receiver": "popup" } }, "message": "this._authQueue is null", "file": "moz-extension://4506fb03-26bb-40fa-81d8-68a44cee0295/js/background.js", "line": 2, "stack": "addServer@moz-extension://4506fb03-26bb-40fa-81d8-68a44cee0295/js/background.js:2:748028\n", "time": 1690385180830 }, "error": { "name": "TypeError", "stack": [ "addServer@moz-extension://4506fb03-26bb-40fa-81d8-68a44cee0295/js/background.js:2:748028", "" ], "string": "TypeError: this._authQueue is null", "fileName": "moz-extension://4506fb03-26bb-40fa-81d8-68a44cee0295/js/background.js", "lineNumber": 2, "columnNumber": 748028, "message": "this._authQueue is null" } }
The text was updated successfully, but these errors were encountered: