Result object is undefined, throwing an Error doesn't fire onError. #199
Replies: 1 comment
-
Found the fix to the issue. If your action doesn't return the result, even though you can see it when logging in action middleware. In my case it was setting the response headers in a wrong way. Fixing this, fixed the error. :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, as I don't want to create a new Issue because this error is unexpected I decided to ask for help here.
Suddenly after adding a new feature my actions do not return a result object.
Is there anything I should be aware of when using next-safe-action which may cause this issue?
Excuse my mistakes if any, this is my first time asking for help on GitHub.
Thanks in advance :)
Typescript: 5.4
next-safe-action: ^7.1.3
NextJS: 14.2.4
Action Client:
Action (annotated with 'use server') :
Login form (annotated with 'use client'):
and form
Beta Was this translation helpful? Give feedback.
All reactions