Describe the bug
The REST-API does respond with error messages when it is used before the user has opened the web interface at least one time before.
To Reproduce
Steps to reproduce the behavior:
owner is null)Expected behavior
REST-API can be used fully without opening it in the web interface. Maybe do first initialization stuff as post install hook or when using the REST-API (like checking a flag isInitialized and do initialization if flag is false)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Please keep open @juliushaertl
@stefan-niedermann Do you have the actual log error available?
currently not, but if i am at my notebook back again, i will reproduce this error
Maybe @desperateCoder can explain better what exactly is happening here.
It has been a while since september, i do not remember exactly, but i let a hint there "this can be the case if the Deck app has never before been opened in the webinterface" - and voila - as soon as i opened the deck app on my test user the very first time, this does not happen anymore.
@stefan-niedermann i actually have no idea. safe to close?
No, create a new user, try to connect to it. Does only work, when the web UI for this user has at least been opened once. No log available yet
What do we need? Server response for this case? PHP logs from the server?
I don't see where this would fail on the server side, if the user has never opened the web interface the /boards endpoint will just return an empty array as no default "Personal" board has been created.
I'll prepare a pull request to create the initial board from the API as well, but I guess there is also an issue on the app side here.
Most helpful comment
https://github.com/nextcloud/deck/pull/1492