Error for one deployment but not another
Hey all,
Another team member of mine is getting a 422 error on their deployment when testing out my PR, we hopped on a call, their branch is up to date, server is restarted, and their environment seems to be set up correctly.
Their
Mine is set up the same but for my deployment id, but mine works. We stepped through mine vs his and there doesn't seem to be any environmental or codebase difference, yet we're seeing an error for him and not for me.
To my understand a 422 means that Convex knows the route exists but it's failing.
Some additional context here is that this is specific to user sign-up, and we are using the better-auth integration with Convex. We both are using the same BETTER_AUTH_SECRET, but I don't think that matters either way.
Any leading questions or assitance that can be provided would be a huge help. Thank you!!
Another team member of mine is getting a 422 error on their deployment when testing out my PR, we hopped on a call, their branch is up to date, server is restarted, and their environment seems to be set up correctly.
Their
NEXT_PUBLIC_CONVEX_URL follows the https://<their-deployment-id>.convex.cloud pattern, and their key is their deployment id as well (not a url).Mine is set up the same but for my deployment id, but mine works. We stepped through mine vs his and there doesn't seem to be any environmental or codebase difference, yet we're seeing an error for him and not for me.
To my understand a 422 means that Convex knows the route exists but it's failing.
Some additional context here is that this is specific to user sign-up, and we are using the better-auth integration with Convex. We both are using the same BETTER_AUTH_SECRET, but I don't think that matters either way.
Any leading questions or assitance that can be provided would be a huge help. Thank you!!
