"Intercepting routes" feature not working in production

[478732]

Link to the code that reproduces this issue

https://github.com/478732/temp

To Reproduce

1. Visit https://resplendent-halva-bdccd9.netlify.app/
2. Click on the text, "Image 1"
3. You will be taken to another page

Current vs. Expected behavior

Current behavior

1. On https://resplendent-halva-bdccd9.netlify.app/
2. When you click on the text, "Image 1"
3. You will be taken to another page

Expected behavior

1. On https://resplendent-halva-bdccd9.netlify.app/
2. When you click on the text, "Image 1"
3. Black box should appear

Description

I am trying to make a feature where

when you click on a specific element, a black box appears.

To make this feature, I am using the "intercepting routes" feature.

It works fine locally, but does not work in production.

Locally, on localhost:3000, when I click on the text "Image 1", a black box appears.

However, in production at https://resplendent-halva-bdccd9.netlify.app/

when I click on the text, "Image 1", I am taken to another page (unexpected)

A black box should be appearing.

My code is similar to vercel's nextgram app found at https://github.com/vercel/nextgram

Video showing problem

demo.mov

Provide environment information

- MacOS
- NextJS 14.1
- Google Chrome

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

Other (Deployed)

Additional context

No response

[CalebMacdonaldBlack]

It's an issue with netlify

netlify/next-runtime#2089

[DanhezCode]

I have the same problem in version 14.2.4 with a code very similar to this one, it works well in the development environment but in the production environment after doing the build it redirects me without showing the modal and it does it locally when using the start command instead of dev without deploying to any hosting

[DanhezCode]

After several hours of troubleshooting, I discovered the error. The solution lies in how the folder name was being declared for interception. I was using a folder named (.)/signin because I had interpreted that this was the correct way to set up the interception. However, the correct approach is to create a folder named (.) and within this folder, place another folder named signin.

The creator of this issue is making the same mistake I did. If they change (.)/photos/[id] to a folder named (.) and place the other folders inside it, in the respective order of photos and [id], it will work.