Getting ready for liftoff
planned
Maud Miguet
planned
Maud Miguet
Hi Brian,
We'll look into that. Can you tell me more about when it happens to you?
You had Chrome closed, you open it and Station opens with the loading logo without you triggering it?
Or do you mean when you open it with the keyboard shortcut, it often has the loading logo?
Brian Terry
Maud Miguet:
You had Chrome closed, you open it and Station opens with the loading logo without you triggering it?
Almost, I have Station set up to load as my home page as soon as Chrome opens. Sometimes the loading of Station appears to get stuck and all I see is the logo and "Getting ready for liftoff" message.
Then when I open a new tab everything is fine and I can see all apps and pages Station has bookmarked from each app and website.
When I launched Chrome this morning for the first time Station worked fine and my Chrome home screen showed station load for a second before showing the apps and everything else.
The only keyboard shortcut I'm using is to open a new tab.
If it happens again I'll let you know.
Does this help?
Brian Terry
Hi @Maud Miguet - I think I've narrowed this down some more.
When I quit Chrome then open again the Station load screen becomes stuck with the "Getting ready for liftoff" message. As I described above.
Station loads fine on Chrome's first launch after the start-up of my Mac. But when I quit Chrome after this, then re-launch Chrome the issue of Station being stuck in the "Getting ready for liftoff" loop I described above occurs.
Maud Miguet
Brian Terry: Thanks for all the precisions. I'm trying to reproduce the problem but I'm not able to. When Station has its infinite loading, can you please check your console logs and send them to us?
You can follow the instructions written here (step II and III): http://faq.stationhq.com/en/articles/4263322-how-can-i-send-you-a-bug-report-for-investigation
Brian Terry
Maud Miguet: Thanks for explaining how to do this.
Here's a screenshot of the console logs when this is happening.
I'm finding I get this error every time I launch Chrome except for the first launch after a MacOS system restart.
I hope this makes sense to someone ;)
Thanks!