Nextjs 12, 13 with geo in middleware

Hey @pob944,

1. Make sure that the geo property is being set correctly in the nextUrl object. You can check this by logging the geo property to the console in your middleware function.

2. Check that the user’s location can be determined using the geo property. You can do this by logging the latitude and longitude properties of the geo object to the console.

3. If the user’s location cannot be determined, you can use a fallback location as a default value for the city variable. For example, you can set const city = geo?.city ?? 'Canada'; to set the city variable to “Canada” if the geo object does not contain a city property.

4. Check that the cookie is being set correctly: Make sure that the cookie is being set correctly by logging the cookie value to the console or using a browser extension like “EditThisCookie” to inspect the cookie.

I’ve not used Nextjs however this should work eitherway :

export default async function middleware(req: NextRequest) {
  const { nextUrl: { geo } } = req;

  const city = geo?.city ?? 'Canada';

  const res = NextResponse.next();
  res.cookies.set('city', city);

  return { req, res };
}

Hope I help even a little bit!

Hey @pob944,

1. Make sure that the geo property is being set correctly in the nextUrl object. You can check this by logging the geo property to the console in your middleware function.

2. Check that the user’s location can be determined using the geo property. You can do this by logging the latitude and longitude properties of the geo object to the console.

3. If the user’s location cannot be determined, you can use a fallback location as a default value for the city variable. For example, you can set const city = geo?.city ?? 'Canada'; to set the city variable to “Canada” if the geo object does not contain a city property.

4. Check that the cookie is being set correctly: Make sure that the cookie is being set correctly by logging the cookie value to the console or using a browser extension like “EditThisCookie” to inspect the cookie.

I’ve not used Nextjs however this should work eitherway :

export default async function middleware(req: NextRequest) {
  const { nextUrl: { geo } } = req;

  const city = geo?.city ?? 'Canada';

  const res = NextResponse.next();
  res.cookies.set('city', city);

  return { req, res };
}

Hope I help even a little bit!

Hey @pob944,

I’ve not used NextJS however here is what I would do if I had to troubleshoot this and see why it doesn’t work :

1. Make sure that the geo property is being set correctly in the nextUrl object. You can check this by logging the geo property to the console in your middleware function.

2. Check that the user’s location can be determined using the geo property. You can do this by logging the latitude and longitude properties of the geo object to the console.

3. If the user’s location cannot be determined, you can use a fallback location as a default value for the city variable. For example, you can set const city = geo?.city ?? 'Canada'; to set the city variable to “Canada” if the geo object does not contain a city property.

4. Check that the cookie is being set correctly: Make sure that the cookie is being set correctly by logging the cookie value to the console or using a browser extension like “EditThisCookie” to inspect the cookie.

As said I’ve not used Nextjs however this should work either way:

export default async function middleware(req: NextRequest) {
  const { nextUrl: { geo } } = req;

  const city = geo?.city ?? 'Canada';

  const res = NextResponse.next();
  res.cookies.set('city', city);

  return { req, res };
}

Hope I help even a little bit!