App hangs on loading UI when trying to create a book
[Provide a general summary of the issue in the title above]
Expected behavior
User can create a book from "Start writing your book" and "Import your files" buttons on the Dashboard
Current behavior
@Carra
Case 1 fromWe released the newest version of Ketty today and we are still experiencing some problems that seem connected to this issue.
-- When starting a new book via Import the process stalls right away.
-- Within an existing book, starting a new chapter via Import also stalls. I get so far as to pick the file to import but it never gets past 'processing' I was able to import one chapter, so this bug doesn't always occur.
@ckepper
Case 2 fromI experienced a slight variation of the problem that Carra described. I was using Safari (Version 17.2.1 (19617.1.17.11.12)) because I wanted to record a screencast. The problem only occurred on our installation (https://ketty.lulu.com) not on the public Coko server (https://ketida.cokodemo.net/).
After registering a new account, I tried to create a new book (both via import and via "Start writing your book"). At that point the UI stalled at the loading animation just like in Carra's screenshots.
I was still able to click the "Start writing your book" and "Import your files" buttons, but the animation didn't go away. After using "Reload" to refresh the page, the new book was there.
The browser console shows the following error: WebSocket connection to 'wss://ketty-api.lulu.com/subscriptions' failed: The operation couldn’t be completed. Socket is not connected
Steps to reproduce
- Create a book from "start writing your book" or "import your files"
- See creating hangs and does not progress to Producer page
- Refreshing shows the book was created as it's listed on the Dashboard
Environment
- Client (Lulu) deployment of Release 2.2.1
QA Elimination Steps
-
Test subscriptions in isolated environment (the coko client dev playground) -
Test subscriptions using a cluster of 3 servers -
Revert workaround (noted here) and test subscriptions in ketty -
Get all deployment setup details from Lulu to validate that the issue is not due to the instance configurations -
Live replication debugging with Lulu
If none if the above is successful we'll need to replicate Lulu deployment setup and test further.
Possible solution
[Not required. Suggest a fix for the bug]