Hi please don’t make a new post. Just bumping this post is good. Reposts are against our rules

Okay

To answer your question: https://nextjs.org/docs/app/building-your-application/optimizing/metadata

I tried it but it didn't work

what are you trying to accomplish and what's it currently doing?

I'm trying to set a favicon for my next js app.....I followed next js docs steps and I put the favicon.ico within the app/ directory but in browsers my favicon is not shown

favicon.ico needs to go in the public/ directory, otherwise it won't be accessible to the client

This is wrong, app/favicon.ico is fine

there's probably a way to do it within the app router, given that's what's on the documentation. i've always just had it in the public folder though (same location as the default favicon.ico) and that seems to work

For the app router only

Try a fresh new browser

This is likely due to browser caching

^this

Browsers cache favicons pretty aggressively

@joulev do you know how long ago that app router support for favicons got added?

i honestly had no idea that was a thing

I think it was about the same time the whole metadata thing was released

13.2 or 13.3

interesting

I don’t remember exactly what version but should be one of those two

kinda cool ngl

So should I clear the browser cache??

Okay

It works fine in dev mode

But not in production