nemo
nemo
PostsComments
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
Not undefined. Sometimes it logs the redirect URI, and sometimes or most of the times, nothing is getting logged for some reason. Maybe something with the middleware?
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
Not sure why! But the data is empty. Sorry. I got so frustrated that I stopped working on it for a while.
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
In the callback, data does not log anything because Supabase is throwing the error and the error is getting logged.
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
Yes. Both have the same base URL.
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
No. I changed nothing. Restarted my PC just in case. Worked once, then back to this. Could be some issue with local environment? Ref: https://github.com/supabase/supabase/discussions/21183#discussioncomment-12293822
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
I can't wrap my head around on how it worked last night!
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
No. It's not available before exchange also.
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
Tried logging like this: 
auth.get("/oauth/google/callback", async (c) => {
  const code = c.req.query("code");
  console.log("getCookie", getCookie(c));
auth.get("/oauth/google/callback", async (c) => {
  const code = c.req.query("code");
  console.log("getCookie", getCookie(c));
And getting empty array.
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
So last night it worked fine. And in the morning, some energy decided to kill my energy and started giving me a new error which is from Supabase actually: 
invalid request: both auth code and code verifier should be non-empty
invalid request: both auth code and code verifier should be non-empty
Someone provided a solution on Github, however, I am not quite sure on how to implement it on hono: https://github.com/orgs/supabase/discussions/21183#discussioncomment-11877084 Sorry for pinging you @ambergristle , but do you have any idea why the link I shared above works?
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
Found the solution. Thank you guiding me. I used the middleware like this: 
app.use("*", supabaseMiddleware());
app.use("*", supabaseMiddleware());
Then tweaking the code like this worked: 
import { Hono } from "hono";
import { getSupabase } from "../middlewares/supabase";
import { envs } from "../config/envs";

const auth = new Hono();

auth.get("/oauth/google", async (c) => {
  const supabase = getSupabase(c);

  const { data, error } = await supabase.auth.signInWithOAuth({
    provider: "google",
    options: {
      redirectTo: `${envs.authServiceUrl}/auth/oauth/google/callback`,
    },
  });

  if (error) {
    return c.json({ error: error.message }, 400);
  }

  c.status(301);
  c.redirect(data.url);

  return c.json({ data });
});

auth.get("/oauth/google/callback", async (c) => {
  const code = c.req.query("code");

  if (!code) {
    return c.json({ error: "Authorization code is missing" }, 400);
  }

  const supabase = getSupabase(c);

  const { data, error } = await supabase.auth.exchangeCodeForSession(code);
  const { session } = data;

  if (error) {
    return c.json({ error: error.message }, 400);
  }

  return c.json({
    message: "User session retrieved successfully",
    session,
  });
});

export default auth;
import { Hono } from "hono";
import { getSupabase } from "../middlewares/supabase";
import { envs } from "../config/envs";

const auth = new Hono();

auth.get("/oauth/google", async (c) => {
  const supabase = getSupabase(c);

  const { data, error } = await supabase.auth.signInWithOAuth({
    provider: "google",
    options: {
      redirectTo: `${envs.authServiceUrl}/auth/oauth/google/callback`,
    },
  });

  if (error) {
    return c.json({ error: error.message }, 400);
  }

  c.status(301);
  c.redirect(data.url);

  return c.json({ data });
});

auth.get("/oauth/google/callback", async (c) => {
  const code = c.req.query("code");

  if (!code) {
    return c.json({ error: "Authorization code is missing" }, 400);
  }

  const supabase = getSupabase(c);

  const { data, error } = await supabase.auth.exchangeCodeForSession(code);
  const { session } = data;

  if (error) {
    return c.json({ error: error.message }, 400);
  }

  return c.json({
    message: "User session retrieved successfully",
    session,
  });
});

export default auth;
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
Now I got this 😅 : 
error: Context is not finalized. Did you forget to return a Response object or `await next()`?
error: Context is not finalized. Did you forget to return a Response object or `await next()`?
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
That is mostly private code, and that one is using ElysiaJS. But to give you some idea: 
.get("/oauth/google", async (context) => {
        const { data, error: err } = await supabase.auth.signInWithOAuth({
          provider: "google",
          options: {
            redirectTo: `${envs.authServiceUrl}/auth/oauth/google/callback`,
          },
        });

        console.log("data.url", data.url);

        if (err) {
          logger.error(err, "Error initiating Google OAuth");
          return error(
            500,
            res(
              false,
              "Failed to initiate Google authentication",
              null,
              err.message
            )
          );
        }

        // Redirect user to Google's authentication page
        return new Response(null, {
          status: 302,
          headers: {
            Location: data.url,
          },
        });
      })
      .get("/oauth/google/callback", async (context) => {
 
}
.get("/oauth/google", async (context) => {
        const { data, error: err } = await supabase.auth.signInWithOAuth({
          provider: "google",
          options: {
            redirectTo: `${envs.authServiceUrl}/auth/oauth/google/callback`,
          },
        });

        console.log("data.url", data.url);

        if (err) {
          logger.error(err, "Error initiating Google OAuth");
          return error(
            500,
            res(
              false,
              "Failed to initiate Google authentication",
              null,
              err.message
            )
          );
        }

        // Redirect user to Google's authentication page
        return new Response(null, {
          status: 302,
          headers: {
            Location: data.url,
          },
        });
      })
      .get("/oauth/google/callback", async (context) => {
 
}
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
Then the SSR package from Supabase should help? But the terrible documentation is making me realize again and again how dumb I am.
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
I am not able to get anything after the #
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
Right now it's part of nothing. I am trying to make OAuth work in the server-side with Supabase. Was following there guide here: https://supabase.com/docs/guides/auth/server-side/creating-a-client?queryGroups=framework&framework=hono&queryGroups=environment&environment=server-client It's just a dummy route. Without SSR, I am able to get till the callback URL part. But at that point, supabase sends the access token in a format like this: http://localhost:3000/auth/oauth/google/callback#access_token=eyJhbGci...&expires_at=1742897402&expires_in=3600&provider_token=ya29.a0AeXRPp6z, now I can't get the access token to exchange it for a session. That's my primary problem.
65 replies
HHono
Created by nemo on 3/25/2025 in #help
Hono Supabase OAuth Error
It's bun. When hitting the endpoints, I'm getting the error. Also, this typing is suggested by the official Supabase team.
65 replies