"Unmatched Route" error on a route that DOES exist.

Please provide the following:

  1. SDK Version: "~48.0.15"
  2. Platforms(Android/iOS/web/all): android

here is my app dir structure:

├── index.js
├── _layout.js
├── packs
│   └── index.js
├── profile
│   └── index.js
└── trips
    └── index.js

As you can see the trips route exists, but take a look at the screenshot below: it throws “Unmatched Route” on /trips.

I’ll appreciate your help, thanks.

Edit: The route works on web; the error only occur on mobile.

Tried reproducing your example, and it is working for me. Make sure, if the file route is named trips then the route is also /trips (just assuming that sometimes it can be a case sensitive issue with file routing systems). However, if that’s not the case, please share a minimal reproducible example and I’m happy to take a look.

1 Like

Hey @amanhimself, thanks for showing help. The routes I provided aren’t actually complete, I’ll attach a screenshot of the directory with all the routes. I omitted them because I don’t see how they might be the cause of the issue. And the fact that it works on the web shows that there’s nothing wrong with the route namings. Additionally the trips route doesn’t show in the sitemap -when i click “Sitemap” on the error page. And to make it even more strange, everything was working fine the day before.

I thought it has to do with cache or something, but even wiping the apps data and uninstalling and installing it again couldn’t solve the problem.


This can occur if there’s an error inside the trips/index file. Please provide source that we can run for the minimum reproducible example otherwise we cannot investigate further.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.