The output returned by confirmSignUp has signUpStep:'DONE' and not signUpStep:'COMPLETE_AUTO_SIGN_IN'.

[adithyavis]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework

React Native

Amplify APIs

Authentication

Amplify Version

v6

Amplify Categories

auth

Backend

Amplify CLI

Environment information

# Put output below this line
System:
    OS: macOS 15.2
    CPU: (11) arm64 Apple M3 Pro
    Memory: 151.50 MB / 18.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.11.0 - ~/.nodenv/versions/22.11.0/bin/node
    Yarn: 1.22.22 - ~/.nodenv/versions/22.11.0/bin/yarn
    npm: 10.9.0 - ~/.nodenv/versions/22.11.0/bin/npm
    Watchman: 2024.10.28.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 131.0.6778.205
    Edge: 131.0.2903.112
    Safari: 18.2
  npmGlobalPackages:
    appcenter-cli: 3.0.3
    corepack: 0.29.4
    npm: 10.9.0
    yarn: 1.22.22

Describe the bug

I have autoSignIn: true option set while calling signUp method. signUpVerificationMethod is set to 'code'.
Upon clicking on the verification link, my app is opened and confirmSignUp method is invoked with the email and code obtained from the link.
The signUpStep in the result of calling confirmSignUp is "DONE" instead of "COMPLETE_AUTO_SIGN_IN", hence autoSignIn is not possible.

Expected behavior

The signUpStep in the result of calling confirmSignUp should be "COMPLETE_AUTO_SIGN_IN"

Reproduction steps

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

[cwomack]

Hello, @adithyavis 👋. Can you share the frontend code that's calling the signIn() and signUp API's? The issue description states that you're on v6, but if you're setting autoSignIn: true within your sign up then that sounds like it's the v5 implementation of Auth.signUp() (see here).

If you could the the frontend code as well as your package.json so we can see the versions of your dependencies, that would help! Thanks.

[adithyavis]

Hey @cwomack, thanks for commenting. Actually we do use v6, and the docs for v6 state that autoSignIn: true is how autoSignIn is configured, as against autoSignIn: {enabled:true} for v5.

Sharing our code like you requested. Would be glad to provide you any further assistance as well

• package.json

    "@aws-amplify/react-native": "^1.1.6",
    "@aws-amplify/rtn-web-browser": "^1.1.1",
    "aws-amplify": "^6.9.0"

• Amplify config

      signUpVerificationMethod: 'code'

• signup

     const response = await Auth.signUp({
        username,
        password,
        options: {
          userAttributes: {
            email: username,
          },
          autoSignIn: true,
        },
      })
   if(response.nextStep.signUpStep === "CONFIRM_SIGN_UP") {...}

• confirmSignUp

     const response = await Auth.confirmSignUp({
        username,
        confirmationCode: code,
      })
     if (response.nextStep.signUpStep === "COMPLETE_AUTO_SIGN_IN") {
         // ===> block gets skipped
     } else if (response.nextStep.signUpStep === "DONE")  {
         // ===> block is executed
     }

[AllanZhengYP]

Hi @adithyavis

Thanks for the code snippet. Can you confirm the username is strictly matched in both signUp and confirmSignUp APIs?

Furthermore, can you confirm your verification method? If you are verifying through a link, then your signUpVerificationMethod should set to "link"; If it's "code", then you should not re-launch your app, otherwise the state storing your code auto sign in information will be wiped out.

[adithyavis]

Hi @AllanZhengYP
Cross-checked, the usernames were not matching. Thanks. Fixed that.
But now when we call autoSignIn(), it leads to this error
UserAlreadyAuthenticatedException: There is already a signed in user.

[AllanZhengYP]

@adithyavis Glad to hear that!

Yes we had verification before any sign-in attempt. If you see this error, you may sign out the user before signing in.