In routes.js webhooks(app); is currently called after the routes.json is loaded. This presents a problem when routes.json includes a catch-all route like:
If I move the webhooks load before routes.json, my problem is solved:
Can this be a permanent change in routes.js?
Until this is solved by Wappler you can use a custom route that loads after the webhooks.
I just ran into this issue as well. Seems like a simple fix that would help ensure others do not waste time investigating when they’ve setup a 404 page in their routes.
Fixed in Wappler 6.1.1
