[slhck]

Just saw this, and as a small business owner in the B2B market, this sounds very useful. Gmail's existing spam filters do not reliably detect this type of marketing.

I wish your landing page had a simple "how it works" explanation with a screen shot or diagram, rather than forcing me to sign in directly, and also allowing the app to read *and* send emails. Also, I don't see any pricing?

Finally, signing up, I got an error:

Error 1101 Ray ID: 89d4e0957c2f5a44 • 2024-07-03 06:39:15 UTC - Worker threw exception

[louwhopley]

Thanks for the useful feedback! Totally forgot that pricing was never added to the landing page → have added to the todo list to fix up.

Where in the process did that error occur for you?

I see in the logs that an error registered, but unfortunately no detail attached. I've beefed up the logging a bit in the onboarding journey on my side to see what could be breaking here if we try again.

Mind trying to log-in/sign up again? You can use "HACKERNEWS" as a promo code, which would make the first month free.

[slhck]

The error occurred right after granting permissions from my Google account. The permissions were granted but I could never access your application page. I just tried again, now I got an "Error handling OAuth callback" after granting permissions. Signing in again does not work either. (I did remove all of the app's permissions in my Google security settings before, so to Google it looked like the application was requesting all of its permissions again.)

[louwhopley]

I do see it in the logs now. So weird, as dozens of people successfully signed up without this issue. Have added more logs now again to double down on that specific area where this issue is caused. Maybe another login attempt now will be able to uncover the gap.

Thanks for removing the permissions in Google, as that's also key in this debugging.

Mind if I send you an email to debug further there?

[louwhopley]

Quick shoutout to slhck for helping me debug and resolve this issue. Thank you!

tl;dr: Ran into issues because the DB was expecting a profile picture URL from Google auth (string) or NULL, but JavaScript being JavaScript tried to insert "undefined".