BA
Better Auth•2mo ago
basic white guy

callbackOnVerification receives user as null

I'm running into an issue where callbackOnVerification is getting user as null after phone verification.
user in callbackOnVerification is coming back as null, making it impossible to update the database with the verified phone number.
Handling OTP Verification: 
const handleVerifyOTP = async () => {
  await authClient.phoneNumber.verify(
    {
      phoneNumber: form.getValues("phoneNumber"),
      code: pin,
      // disableSession: true,  // TODO: make sure if needed 
    },
    {
      onError: (error) => {
        toast({
          title: "OTP Verification Failed",
          description: error.error.message,
          variant: "destructive",
        });
      },
      onSuccess: () => {
        toast({
          title: "OTP Verified",
          description: "Your OTP has been verified successfully",
          variant: "default",
        });
        navigate({
          to: "/dashboard",
          replace: true,
        });
      },
    }
  );
};
const handleVerifyOTP = async () => {
  await authClient.phoneNumber.verify(
    {
      phoneNumber: form.getValues("phoneNumber"),
      code: pin,
      // disableSession: true,  // TODO: make sure if needed 
    },
    {
      onError: (error) => {
        toast({
          title: "OTP Verification Failed",
          description: error.error.message,
          variant: "destructive",
        });
      },
      onSuccess: () => {
        toast({
          title: "OTP Verified",
          description: "Your OTP has been verified successfully",
          variant: "default",
        });
        navigate({
          to: "/dashboard",
          replace: true,
        });
      },
    }
  );
};
Auth configuration (callbackOnVerification issue):
callbackOnVerification: async ({ phoneNumber, user }) => {
  // user is null here
  console.log("~ data, request:", phoneNumber, user);

  await db
    .update(UserTable)
    .set({ phoneNumberVerified: true, phoneNumber })
    .where(eq(UserTable.id, user?.id ?? ""));
};
callbackOnVerification: async ({ phoneNumber, user }) => {
  // user is null here
  console.log("~ data, request:", phoneNumber, user);

  await db
    .update(UserTable)
    .set({ phoneNumberVerified: true, phoneNumber })
    .where(eq(UserTable.id, user?.id ?? ""));
};
Question: Is there a way to ensure the user object is always available in callbackOnVerification? Could this be related to disableSession: true in handleVerifyOTP, or is there another way to retrieve the user at this stage?
1 Reply
bekacru
bekacru•2mo ago
It returns null when the user hasn't signed up yet, but this should be fixed in the next release. It should only be called if a user exists and also should be called after sign-up if enabled.

Did you find this page helpful?