amplify-js: "No userPool" error starting at aws-amplify@0.1.45

Updated: Sorry, I mixed up the names and versions of aws-amplify and aws-amplify-react. aws-amplify has the versions 0.1.45, etc. aws-amplify has the versions 0.3.x and 0.4.x. Sorry for the confusion.

I just did an update on my dependencies. Noticed I could no longer authenticate with Cognito/aws-amplify/aws-amplify-react. Something in FederatedSignin.js render() method is throwing the “No userPool” error for some reason. If i downgrade to aws-amplify-react@0.1.44, things work.

Specifically, I tracked it down as far as aws-amplify/Auth/AuthClass. For some reason, it is losing its configuration in FederatedSignin.js. All config values are undefined by the time it gets called here in this module.

Looks like there were some major changes between these 2 versions as well. Dependencies changed so that 0.1.45 depends on aws-amplify-react@0.4.0 now. These changes were made just a couple days ago. Just want to report the issue here at least. Unfortunately, perfect timing to get tripped up with this just now.

Thanks, Jae

Working: ├─ aws-amplify-react@0.1.44 ├─ aws-amplify@0.3.4

Broken: ├─ aws-amplify-react@0.1.45 │ ├─ aws-amplify@^0.4.x │ ├─ aws-amplify@0.4.0

ConsoleLogger.js:100 {[DEBUG] 07:10.752 Amplify - amplify config: {…}}
ConsoleLogger.js:84 [DEBUG] 07:10.753 I18n - configure I18n
ConsoleLogger.js:84 [DEBUG] 07:10.753 I18n - create I18n instance
ConsoleLogger.js:84 [DEBUG] 07:13.507 AuthClass - configure Auth
ConsoleLogger.js:100 {[DEBUG] 07:13.507 Parser - parse config: Array(3)}
ConsoleLogger.js:100 {[DEBUG] 07:13.508 Analytics - on hub capsule auth: {…}}
ConsoleLogger.js:84 [DEBUG] 07:13.508 AnalyticsClass - configure Analytics
ConsoleLogger.js:100 {[DEBUG] 07:13.510 Parser - parse config: Array(3)}
ConsoleLogger.js:84 [DEBUG] 07:13.510 AuthClass - getting current credntials
ConsoleLogger.js:84 [DEBUG] 07:13.510 AuthClass - picking up credentials
ConsoleLogger.js:84 [DEBUG] 07:13.512 AuthClass - getting old cred promise
ConsoleLogger.js:84 [DEBUG] 07:13.513 Storage - configure called
ConsoleLogger.js:84 [DEBUG] 07:13.513 StorageClass - configure Storage
ConsoleLogger.js:84 [DEBUG] 07:13.514 StorageClass - configure Storage
ConsoleLogger.js:100 {[DEBUG] 07:13.514 PubSub - configure PubSub: {…}}[DEBUG] 07:13.514 PubSub - configure PubSub: opt: {aws_app_analytics: "enable", aws_auth_facebook: "enable", aws_cognito_identity_pool_id: "us-west-2:44a30419-a324-46c6-94d6-d2ef2b3df6d7", aws_cognito_region: "us-west-2", aws_content_delivery: "enable", …}__proto__: Object__proto__: Object
ConsoleLogger.js:100 {[DEBUG] 07:13.514 API - configure API: {…}}
ConsoleLogger.js:84 [DEBUG] 07:13.515 API - create API instance
ConsoleLogger.js:100 {[DEBUG] 07:13.515 RestClient - API Options: {…}}[DEBUG] 07:13.515 RestClient - API Options: {aws_app_analytics: "enable", aws_auth_facebook: "enable", aws_cognito_identity_pool_id: "us-west-2:44a30419-a324-46c6-94d6-d2ef2b3df6d7", aws_cognito_region: "us-west-2", aws_content_delivery: "enable", …}__proto__: Object
ConsoleLogger.js:84 [DEBUG] 07:13.528 Hub - noname listening auth
ConsoleLogger.js:84 [DEBUG] 07:13.544 AuthClass - getting current authenticted user
ConsoleLogger.js:84 [INFO] 07:13.544 Cache - Get item: key is federatedUser with options undefined
ConsoleLogger.js:84 [DEBUG] 07:13.550 AuthClass - get current authenticated userpool user
ConsoleLogger.js:100 {[DEBUG] 07:13.550 AuthClass - getting session failed: "No current user"}
ConsoleLogger.js:84 [DEBUG] 07:13.552 AuthClass - setting credentials for guest

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 3
Comments: 20 (2 by maintainers)

Most upvoted comments

In my case I forgot to add

import Amplify from 'aws-amplify';
import AppSync from './aws-exports.js';

Amplify.configure({
    Auth: AppSync
});

in index.js

deankostomaj on Dec 26, 2018

I had the same “No userPool” error. Downgrading to these two versions fixed it.

    "aws-amplify": "^0.4.0",
    "aws-amplify-react": "^0.1.46",

thelinuxkid on May 17, 2018

Im still having issue this on

 "aws-amplify": "^1.1.28",
 "aws-amplify-react": "^2.3.8",

junejie on Sep 10, 2019

@avcohen installing aws-amplify@0.4.0 and aws-amplify-react@0.1.46 seemed to resolve this problem for me

jbeard4 on Aug 16, 2018

@mlabieniec i’m aware this was closed but i seem to be having some difficulty getting past this error despite dropping back to aws-amplify@0.4.1 and aws-amplify-react@0.1.47 as noted by @setuk as well as aws-amplify@0.4.0 and aws-amplify-react@0.1.46 as noted by @thelinuxkid.

my implementation doesn’t use awsmobile to generate an aws config file - doing this manually via ~/config.js as per a tutorial. i have confirmed the user i’m attempting to use is CONFIRMED and the userPoolId is associated with the correct identityPoolId.

my repo is here for reference.

avcohen on Jul 2, 2018

@setuk thanks for the update. Yes, working now. I just upgraded to the latest versions.

Previously, the error occured with: “aws-amplify”: “^0.4.0”, “aws-amplify-react”: “^0.1.46”,

Working now with: ├─ aws-amplify-react@0.1.47 │ ├─ aws-amplify@^0.4.1 ├─ aws-amplify@0.4.1

jchang10 on Jun 1, 2018