does it happen only at the first time you navigate, or does it happens everytime?

everytime it happens the same

did you try spamming it or did you try it, every now and then?

is it on prod or dev?

i have a dashboard page which needs to be shown on login... so without login i router.push to login page.. also i show a loading screen when the login data is being checked

now i see the dashboard for 1 sec before propogating

both

every time

maybe that 1 sec is because you need to await fetching the session object on the client

if you don't want that maybe put the fetch session object on the server instead

no fetching data has loading screen

when it was with pages directoy it was working ggood

no fetching data has loading screen
or
no, fetching data has loading screen

i migrated it to app now

i still believe its something that happens in the client.
something is being initialized with useEffect

when user information is being loaded.. loading indicator is being showed

otherwise it won't flash the content if its being handled server-side

does the loading screen worked?

yes but after migration to app directory im facing this issue

yes

i feel the router propogation is delayed

does the URL change instantly after router.push

im not sure how you set it up in pages router and how you would've migrated it to app dir

url dosent change quickly

well what auth lib are you using

it shouldnt cause any issues bec when there is no user in the useState

the router.push will take place

it might be because of whatever happened before router.push

how are you sure that router.push is the cause of the delay

router push only happens when loading:false and user:null

loading:true showing loading indicator

bec before migration the app was running smooth

thats a not so valid reason, you still take responsibility of the code you write. so you must've known if router.push would be the case of the delay

regardless, im not sure what your problem is, maybe try creating a reproducible repository, so that we can understand it better

my bad

i didnt return the <Loader /> component while migrating

so there was a glitch