Open HarshitAnchan opened 1 week ago
@HarshitAnchan, thank you for opening this issue. I'll resolve this when I get the chance.
I found the solution: using
On Sun, 23 Jun 2024 at 16:47, Aftab Rehan @.***> wrote:
@HarshitAnchan https://github.com/HarshitAnchan, thank you for opening this issue. I'll resolve this when I get the chance.
— Reply to this email directly, view it on GitHub https://github.com/aftabrehan/board-wex/issues/1#issuecomment-2184948409, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVGOXO536DEF3CIDUPFAQNDZI2VEBAVCNFSM6AAAAABJXHFE3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUHE2DQNBQHE . You are receiving this because you were mentioned.Message ID: @.***>
I found the solution: using
I'll try it.
Uncaught (in promise) Error: Clerk: The component is not configured correctly. The most likely reasons for this error are:
The "/" route is not a catch-all route. It is recommended to convert this route to a catch-all route, eg: "//[[...rest]]/page.tsx". Alternatively, you can update the component to use hash-based routing by setting the "routing" prop to "hash".
The component is mounted in a catch-all route, but all routes under "/" are protected by the middleware.
To resolve this, ensure that the middleware does not protect the catch-all route or any of its children. If you are using the "createRouteMatcher" helper, consider adding "(.)" to the end of the route pattern, eg: "/(.)". For more information, see: https://clerk.com/docs/references/nextjs/clerk-middleware#create-route-matcher
![Uploading Screenshot 2024-06-22 131002.png…]()