Next.js Discord

Discord Forum

hard navigation problem on azure static web app

Unanswered
Georgian Shepherd posted this in #help-forum
Open in Discord
Georgian ShepherdOP
im using next version 13.5.4, im having a problem with all navigation through the next.js Link component causes hard navigation of the target page. here is the problem, it works fine locally on dev, even when i build it and run it locally. but when it gets published to the azure static web app all client side routing is suddenly hard, which i dont understand.

2 Replies

Georgian ShepherdOP
right, ive just narrowed it down to it being the following error, not sure why its occuring though, im not using getstaticprops:

main-75623049b75f64cc.js:1


GET https://xxxxxxxxxx-staging.westeurope.3.azurestaticapps.net/_next/data/l9oPZQnKxnvs4NkWLk2OF/customer-service/contact.json?slug=contact 404 (Not Found)
fetchRetry @ main-75623049b75f64cc.js:1
getData @ main-75623049b75f64cc.js:1
fetchNextData @ main-75623049b75f64cc.js:1
(anonymous) @ main-75623049b75f64cc.js:1
_getData @ main-75623049b75f64cc.js:1
getRouteInfo @ main-75623049b75f64cc.js:1
await in getRouteInfo (async)
change @ main-75623049b75f64cc.js:1
await in change (async)
push @ main-75623049b75f64cc.js:1
n.<computed> @ main-75623049b75f64cc.js:1
navigate @ 835-7eeabcc02cb1d61f.js:8
(anonymous) @ 835-7eeabcc02cb1d61f.js:8
onClick @ 835-7eeabcc02cb1d61f.js:8
Nb @ framework-0c7baedefba6b077.js:9
Tb @ framework-0c7baedefba6b077.js:9
(anonymous) @ framework-0c7baedefba6b077.js:9
nf @ framework-0c7baedefba6b077.js:9
se @ framework-0c7baedefba6b077.js:9
(anonymous) @ framework-0c7baedefba6b077.js:9
Rk @ framework-0c7baedefba6b077.js:9
Jb @ framework-0c7baedefba6b077.js:9
hd @ framework-0c7baedefba6b077.js:9
fd @ framework-0c7baedefba6b077.js:9
ed @ framework-0c7baedefba6b077.js:9
main-75623049b75f64cc.js:1 Error: Failed to load static props
at /_next/static/chunks/main-75623049b75f64cc.js:1:64124
at async /_next/static/chunks/main-75623049b75f64cc.js:1:75926
at async Router.getRouteInfo (/_next/static/chunks/main-75623049b75f64cc.js:1:75668)
at async Router.change (/_next/static/chunks/main-75623049b75f64cc.js:1:69440)
Georgian ShepherdOP
turned out this is an error in next.js 13.5.4, when downgrading to version 13.4.7 the problem disappeared. definetly a bug.