amplify-js: V6 upgrade causes AuthUserPoolException

@pablovargasosorio can you confirm that you installed @aws-amplify/auth into your project? If so the recommendation is to install aws-amplify package instead and import from it. @aws-amplify/auth is marked for internal use only.

For example

import { Amplify } from 'aws-amplify'
import { signInWithRedirect } from 'aws-amplify/auth' // not '@aws-amplify/auth'
import { Hub } from 'aws-amplify/utils'

I got it working with a hybrid:

    Auth: {
        identityPoolId: config.cognito.IDENTITY_POOL_ID,
        region: config.cognito.REGION,
        userPoolWebClientId: config.cognito.APP_CLIENT_ID,
        mandatorySignIn: false,
        Cognito: {
            userPoolId: config.cognito.USER_POOL_ID,
            userPoolClientId: config.cognito.APP_CLIENT_ID
        }...

I used documentation from the API section blended with the Auth section. All of the Auth options should be under the Auth section in the documentation. And more formally documented with all potential options than just an example.

@natuan62 For me I had to use Amplify.configure() in both a server component and a client component. I’m using Next.js so I put it into my Amplify context file in the initialization process.

Just adding this for reference if others see this because seems like a lot of activity on the thread, This is not related to the config questions, but if you have the problem AuthUserPoolException: Auth UserPool not configured.

If you were using @aws-amplify dependencies before, use the aws-amplify single import instead for 6.0.2+

BEFORE

AFTER

@nadetastic to clarify, things are a bit unclear. A few points:

1. Inconsistent levels of userPoolClientId and userPoolId configuration. Here and here in the documentation the userPool config is two levels down under “Auth” -> “Cognito”. But here it is only one level down, directly under “Auth”. Which is it? It would help to correct it in all places to what it should be.
2. The identity pool config (identityPoolId) is under the top-level “Auth” configuration only. The only place I can see it demonstrated is here that I stumbled upon. And, this identity pool ID is a Cognito identity pool, or regardless if it is a third party identity pool (e.g. Facebook, Google), it is still defined and ID’d through Cognito. Therefore, one could argue it too should be down one level in the “Cognito” JSON config.
3. Not to nitpick, but a suggestion is the definitions of these config elements should be in a formal online document/or dictionary, preferably not scattered through examples. A centralized, ‘API manual’. If there is one somewhere I could not find it, perhaps my mistake. But a formal, central, document reference of every possible configuration element, description, defaults, parameter inputs, options, mins/maxes, possible exceptions, etc.

Thanks for checking and helping improve things.

I still have this issue and cannot figure out how to fix it… using "aws-amplify": "^6.0.28" no matter how I get the Auth not configured error 😦

In my case, the version inconsistency prevented the signOut from working.

  "dependencies": {
    "@aws-amplify/auth": "^6.0.13",
    "@aws-amplify/core": "^6.0.13",
-   "aws-amplify": "^6.0.10"
+   "aws-amplify": "^6.0.13"
  }

Upgrading “aws-amplify” fixed the problem.

Getting same error on "aws-amplify": "^6.0.6"

Amplify.configure({
    Auth: {
            mandatorySignIn: false,
            region: config.cognito.REGION,
            userPoolId: config.cognito.USER_POOL_ID,
            identityPoolId: config.cognito.IDENTITY_POOL_ID,
            userPoolWebClientId: config.cognito.APP_CLIENT_ID
    },
    API: {...

I have reviewed all of the documentation and migration guide and nothing seems out of whack. Help please…

@pablovargasosorio can you confirm that you installed @aws-amplify/auth into your project? If so the recommendation is to install aws-amplify package instead and import from it. @aws-amplify/auth is marked for internal use only.

For example

import { Amplify } from 'aws-amplify'
import { signInWithRedirect } from 'aws-amplify/auth' // not '@aws-amplify/auth'
import { Hub } from 'aws-amplify/utils'

@nadetastic That was the reason of the issue. I changed my package.json

FROM:

"@aws-amplify/auth": "6.0.2"

TO:

"aws-amplify": "6.0.2",

Also changed my imports to use from ‘aws-amplify/auth’, instead of ‘@aws-amplify/auth’ and login works Thank you very much!

I strongly recommend to improve the changelog documentation to let us know the ‘@’ notation is deprecated in V6… Thanks again!

@jgabriel98 I found the cause of my issue. You should be sure 100% you configure amplify - eventually I did it a couple of times - before calling the API (even only to test it, try to call it just before the get or post or whatever call). Just a suggestion, with the other version of amplify same code it wasn’t necessary!

For those still struggling here, it took me a while but I was able to get everything working. I put together a simple demo stripped from my production app. The demo is not functional but it shows the exact amplify configuration, locked package versions for amplify and nextjs as well as both server and client Amplify.configure implementations. If it is not clear or if it would be beneficial for me to complete the demo to make it run, please lmk.

https://github.com/btg5679/amplify6-auth-nextjs-demo

I can confirm this 👍 After removing our used category @aws-amplify/auth and only using aws-amplify it worked for me. They also described the “old” @aws-amplify/auth package as INTERNAL USE ONLY: https://www.npmjs.com/package/@aws-amplify/auth

So, since v6 you need to install the whole “aws-amplify” package. But you can still import from “aws-amplify/auth”

I have done that but am still having the same issue

I’m still having he same issue after trying everything else mentioned in this thread and anywhere else. It is a vue/vite app with pnpm. package.json

	"dependencies": {
		"aws-amplify": "6.0.9",
		"@aws-amplify/pubsub": "6.0.9",
...

main.ts

import type { ResourcesConfig } from "aws-amplify";
import { Amplify } from "aws-amplify";
import { getCurrentUser } from "aws-amplify/auth";

const config: ResourcesConfig = {
	Auth: {
		Cognito: {
			// REQUIRED - Amazon Cognito Identity Pool ID
			identityPoolId: "___",
			// OPTIONAL - Amazon Cognito User Pool ID
			userPoolId: "___",
			// OPTIONAL - Amazon Cognito Web Client ID (26-char alphanumeric string)
			userPoolClientId: "___",
		},
	},
};
Amplify.configure(awsExports);
console.log(Amplify.getConfig());
const authUser = await getCurrentUser(); // This is the line that causes the error

It console logs the proper config then throws an error when calling the getCurrentUser function. Looking in the debugger it seems like the Amplify class that the function is importing from @aws-amplify/core is not the same instance as the one I import from aws-amplify.

@willjstevens thanks for the feedback and context! Let me clarify a bit:

The first and second links in item 1, is the proper way to set up the resources, however it doesn’t clearly show identityPoolId configuration. The third link in item 1 and first link in item 2(link) is a reference to how config would be done previous versions on amplify (v5 and before, the switch under “Choose your framework/language” on the top left)

I’m working to clarify the documentation in Configure Amplify categories (item 1 links) to clearly show how to configure identityPoolId and a few more options 😃

Look at the config structure here. https://github.com/aws-amplify/amplify-js/issues/12627#issuecomment-1848214340

@willjstevens with amplify 6, some of those things need to go under Auth: { Cognito : {} } instead otop level Auth. I don’t remember which ones but check the spec!

@mnovati Thanks for your reply. I can confirm I have it working. I didn’t have any @amplify references in my package.json file. But I did go ahead and delete my node_modules folder and install amplify 6.0.5. Perhaps @amplify references were still kicking about in my node_modules? @nadetastic thanks for investigating - happy to have this sorted.

Can confirm removing individual @aws-amplify packages for each module and using just ONE package: aws-amplify solves this problem.

HI @nadetastic - I can confirm I’ve just run in to this issue as well. I won’t have time until tomorrow to provide more details, but in case helpful, it’s worth mentioning that it occurred when attempting to configure the cognitoUserPoolsTokenProvider and when I removed any references to it, everything worked as expected.