Christian glacet

I've tested to pass the locale I have to the `getScopedI18n` and it seems to work, its a hack that is very ugly as a end user but I wanted...

Another thing I tried that also work (no idea if it makes sense) but I can also set the cookie that is internally used by `getLocaleCache`: ```ts cookies().set("Next-Locale", params.locale); ```...

I've noticed next-intl did use the first strategy ([adding an optional argument that can force the locale]( https://next-intl-docs.vercel.app/docs/environments/metadata-route-handlers#route-handlers)): ```tsx import {NextResponse} from 'next/server'; import {getTranslations} from 'next-intl/server'; export async function...

Ah, sorry, I made a mistake while modifying the path to post this message, my actual file is in the `[locale]` subtree, so A) is not the issue. I confirm...

I think I'm still not getting it right, using `export const dynamic = "force-dynamic";` does indeed render the page at build time, but the result is not kept in cache....

For now, the only solution I found that actually render the route at build time **and** serves a cached version for the first incomming request is to add an optional...

@jakob-fankhauser did you found a solution to this issue?

@jakob-fankhauser Ok that makes sense. I'm not sure how the user device would know the old database should be removed so I guess we should delete it ourselves. I'll investigate...

I think the following should work, I havent checked it yet on production build but it works locally (doesn't seem to appear in Flipper's databases explorer anymore). ```ts import {...

@MacKenzieHnC I tested only on Android for now, also I only tested it locally. I don't know how to check wether it works in store builds.