500 Error When Using Google Integration

Greetings,

After some work I finally got Plausible Analytics up and running. I seem to be having one issue though with the Google integration. When I get redirected back to my site, I see a 500 Error with a nice purple button saying ‘Go to the homepage’. Checking logs I see the following:

18:46:43.168 request_id=FkZNkSl2Y3xRq2sAAABD [warn] Failed to send Sentry event.Cannot send Sentry event because of invalid DSN,
18:46:43.171 request_id=FkZNkSl2Y3xRq2sAAABD [warn] Failed to send Sentry event.Cannot send Sentry event because of invalid DSN,
18:46:43.174 [error] #PID<0.4632.0> running PlausibleWeb.Endpoint (connection #PID<0.4631.0>, stream id 1) terminated,
Server: plausible-analytics.linuxbox.ninja:80 (http),
Request: GET /auth/google/callback?state=1&code=4/0AY0e-g7M62FtUtVgaXeCzliY3c_D_nzA&scope=email%20openid%20https://www.googleapis.com/auth/userinfo.email%20https://www.googleapis.com/auth/webmasters.readonly&authuser=0&prompt=consent,
** (exit) an exception was raised:,
    ** (FunctionClauseError) no function clause matching in String.split/3,
        (elixir 1.10.3) lib/string.ex:471: String.split(nil, ".", []),
        (plausible 0.0.1) lib/plausible_web/controllers/auth_controller.ex:1: PlausibleWeb.AuthController.action/2,
        (plausible 0.0.1) lib/plausible_web/controllers/auth_controller.ex:308: PlausibleWeb.AuthController.google_auth_callback/2,
        (plausible 0.0.1) lib/plausible_web/controllers/auth_controller.ex:1: PlausibleWeb.AuthController.phoenix_controller_pipeline/2,
        (phoenix 1.4.17) lib/phoenix/router.ex:288: Phoenix.Router.__call__/2,
        (plausible 0.0.1) lib/plug/error_handler.ex:65: PlausibleWeb.Router.call/2,
        (plausible 0.0.1) lib/plausible_web/endpoint.ex:1: PlausibleWeb.Endpoint.plug_builder_call/2,
        (plausible 0.0.1) lib/plausible_web/endpoint.ex:1: PlausibleWeb.Endpoint."call (overridable 3)"/2

Any ideas here? Let me know if any further information is needed to troubleshoot!

Thanks,

Bump, I could definitely use some help resolving this issue. If it would be better to open an issue in GitHub I can do so.

Thanks,

Bump, would love to get some support for this issue or is it a bug?