19

I have had the same problem since week ago (haven't tried before that). On Safari Fastmail works.

All requests are 200 OK (there are 2 fewer requests compared to Firefox).
No JS errors in console - I don't see Content Security Policy-related related errors neither compatibility mode enabled or disabled.

If someone has suggestions on what to try either to resolve the issue, or get more information, I'm happy to do some tinkering!

Orion, OS version; hardware type:
MacBook Pro (14-inch, 2021)
macOs Monterey 12.5.1 (21G83)
Version 0.99.119-beta (WebKit 615.1.1)

    Lets try with the new version with different WebKit (coming out today)

    I got it to work with these steps:

    • update Origin to Version 0.99.120-beta (WebKit 614.1.20)
    • clear cookies and localstorage
    • log in again

      Does anyone else has issue with fastmail?

        Confirmed working after updating to Version 0.99.119-beta / clearing cookies / logging in again.

        Thanks!

        6 days later

        I think I'm still seeing this on 0.99.120-beta (WebKit 614.1.20). I've tried nuking cookies, removing the associated index db and local storage, but I seem to get the same splash loading screen without any console messages.

          I'm also still having this issue on one of my machines but not the other, not sure what the difference is... I've tried on both 0.99.120-beta and now 0.99.120.1-beta and still can't get it working after clearing cookies.

            Still not able to reproduce. Just logged into Fastmail, on Ventura using latest Orion, clean install no extensions.

              I'm still seeing this on Version 0.99.120.1-beta (WebKit 614.1.20)

              In the console I get this error:

              TypeError: null is not an object (evaluating 'readabilityResult.textContent')
              checkReadability — Script Element 1:3631
              Global Code — Script Element 1:3648

              Clicking both links takes you to the offending line of code in their mail file:

              if ((readabilityResult.textContent) && (readabilityResult.textContent.length < Readability.prototype.DEFAULT_CHAR_THRESHOLD)) {

              The var readabilityResult is set to null at the top of function checkReadability() which is where the offending line of code exists. So in the code between setting the var to null and attempting to evaluate it in the if statement, readabilityResult is not getting a value that would overwrite null.

              • Vlad replied to this.

                Interestingly, I cleared the cache and deleted cookies, reloaded, and it worked without issue this time.

                  Just managed to get it to load by clearing cookies, cache and local storage—all things I'd tried before 🤷‍♂️ Only thing I'd done differently was first logging in from a private window, which loaded successfully, though not sure how that would make a difference.

                  Definitely seems like some state issue, hopefully just a transient one left from an earlier build though.

                    Glad you got it working!

                      ajgraves readability is the name of the module we use for reader view, I wonder what would case ut to trigger for you on this page.

                          I also had the Fastmail problem — after entering my credentials, the loading wheel would infinitely spin and I couldn't get to my inbox.

                          Inspect Element > Storage > Delete Cookies and Local Storage also worked as a fix for me, with a caveat. When I logged in with "Stay signed in to Fastmail" checked, this fix didn't work — it still resulted in the infinite loading page. When I cleared my cookies and storage again, and logged in without selecting "Stay signed in", the Fastmail inbox loaded right away!

                          On 0.99.120.1-beta

                            letourpowerscombine Same behavior for me. The "Stay signed in" checkbox is the thing that is somehow causing it to not load. Works fine if I don't check it.

                            Version 0.99.120.1-beta (WebKit 614.1.20)

                                whee Excellent catch. I wasn't able to reproduce this before, but I have the same problem if "Stay signed in" is checked.