VexoaOriginal post
Rank 1: Thread
Image 1: https://i.imgur.com/Mxr5aiU.png
Code:
import { NextResponse } from "next/server"
import client, { Account, ID } from "@/lib/appwrite/appwrite"
export async function GET(request: Request) {
// Parse the URL and get the query parameters
const url = new URL(request.url)
const userId = url.searchParams.get("userId")
const secret = url.searchParams.get("secret")
if (!userId || !secret) {
return NextResponse.redirect(process.env.NEXT_PUBLIC_APP_URL || "", 302)
}
try {
const updateURL = Account.updateMagicURLSession(userId, secret)
updateURL.then(
function (response) {
console.log(response)
return NextResponse.redirect(
process.env.NEXT_PUBLIC_APP_URL + "/dashboard",
302
)
},
function (error) {
console.log(error)
throw new Error(error.message)
}
)
// return NextResponse.redirect(
// process.env.NEXT_PUBLIC_APP_URL + "/dashboard",
// 302
// )
} catch (error) {
// console.error(error)
return NextResponse.redirect(process.env.NEXT_PUBLIC_APP_URL || "", 302)
}
// return NextResponse.redirect(
// process.env.NEXT_PUBLIC_APP_URL + "/dashboard" || "",
// 302
// )
}```
Summary
The user is experiencing an issue with updating MagicURL in NextJS v13. They are building their frontend with Next.js 13 and have set it up as static generated files. However, they are facing difficulties with server-side rendering and the persistence of the session cookie. They are unsure of how to implement Magic URLs. Another user suggests using an API route that is executed server-side. The user shares a code snippet for a GET request, but it is unclear if the code is being executed server-side. The error message includes a screenshot and the code for reference.
Solution:
- Disable server-side rendering if not necessary as it can comp