4 ms·

I'm sorry, but there are two seemingly redundant popups in our sign-up process right now. You have to auth via Google twice–once to sign up, and once to authori

by dvdsgl 8y ago

I'm sorry, but there are two seemingly redundant popups in our sign-up process right now. You have to auth via Google twice–once to sign up, and once to authorize Google Drive. This should be fixed this week.

pdxandi 8y ago
I believe my issue is different. I wasn't seeing the normal Google auth screen; I signed-out to see if there was an account sync issue, and I can't seem to sign back in now. I click sign-in, the normal Google auth screen pops-up, I select my account, and the button in the bottom-left corner gets stuck on "Signing in..."
- dvdsgl 8y ago
  Ok perhaps we are being inundated with signups right now, looking into our Firebase auth backend...
  - pdxandi 8y ago
    There are worse problems to have. ;)
- jassmith87 8y ago
  Hey man, can you give me the developer console output. I am very curious what the issue here is, sometimes we have seen extensions like ghostery interfere with the login process but I'm guessing you already would have checked that considering this is HN :)
  - pdxandi 8y ago
    Yeah, I looked through the console. The only log is one analytics script that was blocked: GET https://cdn.segment.com/analytics.js/v1/s5swIuWdyLEwzdp3HXwcaxYXUbi5Bnzu/analytics.min.js https://cdn.segment.com/analytics.js/v1/s5swIuWdyLEwzdp3HXwc... net::ERR_BLOCKED_BY_CLIENT
    - jassmith87 8y ago
      What browser are you using?
    - pdxandi 8y ago
      I'm using Chrome 72.0.3626.109 (64-bit) on OS X 10.14.