Auth SignUp auto send another request and throw Error: No credentials, applicationId or region #3484

namnh06 · 2019-06-19T02:11:18Z

** Which Category is your question related to? **
Auth
** What AWS Services are you utilizing? **
Cognito
** Provide additional details e.g. code snippets **
I have 2 projects which are using the same code like this:
Auth.signUp({ username, password, attributes }).then(data => console.log(data)).catch(error => console.log(error)).finally(() => console.log('done'));
Just like this: https://aws-amplify.github.io/docs/js/authentication#sign-up
Here is the problem show out:

In my old project, everything is ok, just 1 request is sign up send to AWS and got some data from it: https://cognito-idp.ap-southeast-2.amazonaws.com/
In my new project, I have another request go to AWS after the sign up request. There are:
https://cognito-idp.ap-southeast-2.amazonaws.com/
And : https://cognito-identity.ap-southeast-2.amazonaws.com/ which is after the first one and its response is :

message: "Unauthenticated access is not supported for this identity pool."
__type: "NotAuthorizedException"

After that, I got the error in console: Error: No credentials, applicationId or region.

Not sure why is the old project is working fine but with this one, this error show up. Is it because the different in amplify ?

Thanks.

The text was updated successfully, but these errors were encountered:

namnh06 · 2019-06-19T08:35:01Z

After trying and creating some new project, I notice that every new project got this issues:

Error: No credentials, applicationId or region

I thought there are some changes in Amplify JS ?

laurib · 2019-06-19T12:58:25Z

Run into same problem with new project

gerrytsui · 2019-06-19T14:32:36Z

Same here. Starting to get this today from the ng e2e, which tests Auth signin workflow. ( I was fine just yesterday)
"ERROR" Error: Uncaught (in promise): Error: No credentials, applicationId or region

while deployed project is working fine. Very strange.

jdavidhermoso · 2019-06-19T14:52:05Z

+1.

Everything seems to be working fine, but that message appears in console.

gerrytsui · 2019-06-19T15:05:44Z

Here is what I found so far. ( in my case)
The Uncaught exception is from AWSPinpointProvider.ts ( line 155 record function: public async record(params, handlers: PromiseHandlers) { } )

As soon as I disabled Analytics in my project, it works fine without the error.

I agree the app may works fine for you, but it is not passing my ng e2e testing with that exception.

The fact that there is no code change in my project. I believe it is a change on AWS Pinpoint REST API, combined with obviously, uncaught exception, and caching of credential in my old projects.

sammartinez · 2019-06-19T17:51:12Z

@namnh06 Can you provide a copy of your package.json, I want to verify which version you are experiencing this on. Even with creating a new project I would just like to see. Also, can you see about using the latest unstable version running npm install --save aws-amplify@unstable or yarn add aws-amplify@unstable depending on your build system you are using. Prior to installing the unstable version, see about doing a full removal of your node_modules and any lock files you have e.g. yarn.lock or package-lock.json

laurib · 2019-06-19T18:11:04Z

I get same error with aws-amplify@unstable. Also happens with Auth.signIn()
I have only Auth added to backend

gerrytsui · 2019-06-19T18:31:41Z

I found the conditions that is causing the AWSPintpointProvider.ts error.

IF I import Analytics from '@aws-amplify/analytics'; even if I don't use it at runtime ( in our project we call analytics.record only in production mode set by environment.prod.ts )
AND the JSON to Amplify.configure is missing the "Analytics" settings ( again we conditionally add the analytics json using Object.assign to add the analytics configs at runtime)

THEN the Uncaught exception will appear.

The exception start to appear today, an is likely because we upgraded to the latest amplify (stable) sometime this week.

versions details ( everything are the latest stable except TypeScript is at 3.4.5)
"@aws-amplify/analytics": "^1.2.17",
"@aws-amplify/api": "^1.0.36",
"@aws-amplify/auth": "^1.2.25",
"@aws-amplify/ui": "^1.0.20",
"aws-amplify-angular": "^3.0.4",

Angular 8.0.3

laurib · 2019-06-19T18:49:53Z

My aws-exports.js file is

const awsmobile = {
    "aws_project_region": "...",
    "aws_cognito_identity_pool_id": "...",
    "aws_cognito_region": "...",
    "aws_user_pools_id": "...",
    "aws_user_pools_web_client_id": "...",
    "oauth": {}
};
export default awsmobile;

Should there be generated Auth: {} ?

I kind of remember that there used to be...

Also tried adding Auth with default configuration and custom configuration

namnh06 · 2019-06-20T02:21:12Z

@namnh06 Can you provide a copy of your package.json, I want to verify which version you are experiencing this on. Even with creating a new project I would just like to see. Also, can you see about using the latest unstable version running npm install --save aws-amplify@unstable or yarn add aws-amplify@unstable depending on your build system you are using. Prior to installing the unstable version, see about doing a full removal of your node_modules and any lock files you have e.g. yarn.lock or package-lock.json

Hi @sammartinez ,
For your information:

New Project:

"aws-amplify": "^1.1.29",
"aws-amplify-angular": "^3.0.4"

Old Project:

"aws-amplify": "^1.1.28",
"aws-amplify-angular": "^3.0.3"

for the whole package.json, you can look at it here: https://gist.github.com/namnh06/336b49acac9edefc4df152a6b3024c46

I tried to remove everything & install aws-amplify with the version like the old one but no luck.

Also, can you see about using the latest unstable version running npm install --save aws-amplify@unstable or yarn add aws-amplify@unstable depending on your build system you are using. Prior to installing the unstable version, see about doing a full removal of your node_modules and any lock files you have e.g. yarn.lock or package-lock.json

Tried it, no luck either.

I thought @gerrytsui was right and wrong, because of if API, so, the old project should be affect too, but there is not.

ilya-bmi · 2019-06-20T07:16:03Z

I get the same error with react native after an update.
aws-amplify@1.1.29
"react": "16.8.3",
"react-native": "0.59.9",

arjunsk · 2019-06-20T07:54:37Z

I had posted a question regarding the same: https://stackoverflow.com/questions/56680112/bad-request-is-returned-when-amplify-is-configured-for-hosted-ui-in-angular-6

namnh06 · 2019-06-20T07:57:43Z

@arjunsk I got one from yesterday, but no luck till now : https://stackoverflow.com/questions/56659183/amplify-auth-signup-auto-send-another-request-and-throw-error-no-credentials-a

jenshandersson · 2019-06-20T16:34:44Z

I got it working by reverting @aws-amplify/analytics to 1.2.16.

"aws-amplify": "1.1.28",
"@aws-amplify/analytics": "1.2.16",

meetfilipe · 2019-06-20T18:52:52Z

I got it working by reverting @aws-amplify/analytics to 1.2.16.
"aws-amplify": "1.1.28",
"@aws-amplify/analytics": "1.2.16",

Can confirm that this works. Thanks!

marianocodes · 2019-06-20T22:53:29Z

I'm experiencing the same issue but I'm not using @aws-amplify/analytics.

meetfilipe · 2019-06-20T22:55:40Z

I'm experiencing the same issue but I'm not using @aws-amplify/analytics.

Are you sure you have not imported the whole aws-amplify package?

marianocodes · 2019-06-20T23:14:01Z

@filipemcg oh oh oh. Thanks for the tip! using only @aws-amplify/core @aws-amplify/auth fixed the problem!

adnan333bd · 2019-06-24T07:22:44Z

we are not using analytics, but updating all imports like the following [no aws-amplify] solved the issue ..

import Amplify from '@aws-amplify/core';
import Auth from '@aws-amplify/auth';
import { Hub } from '@aws-amplify/core';

WhatIsHeDoing · 2019-06-25T11:20:30Z

Disabling as per the docs fixed this for me.

jordanranz · 2019-07-09T19:46:07Z

#3614 should prevent "Error: No credentials, applicationId or region." from occurring when Analytics is not be used or configured.

stale · 2019-08-08T20:26:28Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale · 2019-08-15T20:32:40Z

This issue has been automatically closed because of inactivity. Please open a new issue if are still encountering problems.

pwfcurry · 2019-09-22T10:49:13Z

Disabling as per the docs fixed this for me.

Thanks, this worked!

You can also suppress the warning if disabling analytics doesn't fix the issue:

YellowBox.ignoreWarnings(["No credentials, applicationId or region"]);

nihp · 2020-04-29T09:10:47Z

I am also facing this issue now.

Note: I am not using analytics anywhere while Auth.signIn and Auth.signUp
I am using the below versions.

  "aws-amplify": "^2.2.5",
   "aws-amplify-react-native": "^3.2.2",

sanyashvets · 2020-05-08T12:25:48Z

In your configs:

{
  Auth: {
    identityPoolId: 'REGION_STR:xxxxxxxxxxxxxx', 
    region: 'REGION_STR',
  },
  Analytics: {
    AWSPinpoint: {
      // Amazon Pinpoint App Client ID
      appId: 'xxxxxxxxxxx',
      // Amazon service region
      region: 'us-east-1'
    }
  }
};

MAKE SURE THAT identityPoolId starts from i, NOT FROM I * (thanks for incorrect docs and examples)

nihp · 2020-05-21T06:11:12Z

we are not using analytics, but updating all imports like the following [no aws-amplify] solved the issue ..
import Amplify from '@aws-amplify/core';
import Auth from '@aws-amplify/auth';
import { Hub } from '@aws-amplify/core';

@filipemcg oh oh oh. Thanks for the tip! using only @aws-amplify/core @aws-amplify/auth fixed the problem!

Above solutions not worked for me

I am using aws-amplify and aws-amplify-react-native

aleckzts · 2020-05-30T12:57:11Z

we are not using analytics, but updating all imports like the following [no aws-amplify] solved the issue ..
import Amplify from '@aws-amplify/core';
import Auth from '@aws-amplify/auth';
import { Hub } from '@aws-amplify/core';
@filipemcg oh oh oh. Thanks for the tip! using only @aws-amplify/core @aws-amplify/auth fixed the problem!

Above solutions not worked for me

I am using aws-amplify and aws-amplify-react-native

The following solution is working for me. Have to manually disable Analytics when using with React Native:

import awsconfig from './aws-exports';
Amplify.configure({
    ...awsconfig,
    Analytics: { 
      disabled: true
    }
});

gruckionvit · 2020-08-13T21:10:45Z

This is still an issue, disabling the analytics is not the right solution. Are there any status updates on this? Did anyone figure out what's causing it

github-actions · 2022-03-30T02:05:42Z

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.

sammartinez added Auth Related to Auth components/category Analytics Related to analytics to-be-reproduced Used in order for Amplify to reproduce said issue and removed Analytics Related to analytics labels Jun 19, 2019

sammartinez added pending-close-response-required A response is required for this issue to remain open, it will be closed within the next 7 days. and removed to-be-reproduced Used in order for Amplify to reproduce said issue labels Jun 19, 2019

stale bot removed the pending-close-response-required A response is required for this issue to remain open, it will be closed within the next 7 days. label Jun 19, 2019

yukitaka13-1110 mentioned this issue Jul 1, 2019

No pubsub module applied for subscription. #3568

Closed

stale bot added the pending-close-response-required A response is required for this issue to remain open, it will be closed within the next 7 days. label Aug 8, 2019

bartvollebregt mentioned this issue Aug 12, 2019

User does not exist #3836

Closed

stale bot closed this as completed Aug 15, 2019

elliottower mentioned this issue Jun 29, 2020

Analytics Record [Unhandled promise rejection: Error: No credentials, applicationId or region #6145

Closed

HieronymusLex mentioned this issue Apr 8, 2021

Error: No credentials, applicationId or region when using PinPoint Analytics (Possible dependency version mismatch?) #8053

Closed

github-actions bot locked as resolved and limited conversation to collaborators Mar 30, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Auth SignUp auto send another request and throw Error: No credentials, applicationId or region #3484

Auth SignUp auto send another request and throw Error: No credentials, applicationId or region #3484

namnh06 commented Jun 19, 2019

namnh06 commented Jun 19, 2019

laurib commented Jun 19, 2019

gerrytsui commented Jun 19, 2019

jdavidhermoso commented Jun 19, 2019

gerrytsui commented Jun 19, 2019 •

edited

sammartinez commented Jun 19, 2019

laurib commented Jun 19, 2019

gerrytsui commented Jun 19, 2019

laurib commented Jun 19, 2019 •

edited

namnh06 commented Jun 20, 2019

ilya-bmi commented Jun 20, 2019

arjunsk commented Jun 20, 2019

namnh06 commented Jun 20, 2019

jenshandersson commented Jun 20, 2019

meetfilipe commented Jun 20, 2019 •

edited

marianocodes commented Jun 20, 2019

meetfilipe commented Jun 20, 2019

marianocodes commented Jun 20, 2019

adnan333bd commented Jun 24, 2019 •

edited

WhatIsHeDoing commented Jun 25, 2019

jordanranz commented Jul 9, 2019

stale bot commented Aug 8, 2019

stale bot commented Aug 15, 2019

pwfcurry commented Sep 22, 2019 •

edited

nihp commented Apr 29, 2020 •

edited

sanyashvets commented May 8, 2020

nihp commented May 21, 2020

aleckzts commented May 30, 2020

gruckionvit commented Aug 13, 2020

github-actions bot commented Mar 30, 2022

Auth SignUp auto send another request and throw Error: No credentials, applicationId or region #3484

Auth SignUp auto send another request and throw Error: No credentials, applicationId or region #3484

Comments

namnh06 commented Jun 19, 2019

namnh06 commented Jun 19, 2019

laurib commented Jun 19, 2019

gerrytsui commented Jun 19, 2019

jdavidhermoso commented Jun 19, 2019

gerrytsui commented Jun 19, 2019 • edited

sammartinez commented Jun 19, 2019

laurib commented Jun 19, 2019

gerrytsui commented Jun 19, 2019

laurib commented Jun 19, 2019 • edited

namnh06 commented Jun 20, 2019

ilya-bmi commented Jun 20, 2019

arjunsk commented Jun 20, 2019

namnh06 commented Jun 20, 2019

jenshandersson commented Jun 20, 2019

meetfilipe commented Jun 20, 2019 • edited

marianocodes commented Jun 20, 2019

meetfilipe commented Jun 20, 2019

marianocodes commented Jun 20, 2019

adnan333bd commented Jun 24, 2019 • edited

WhatIsHeDoing commented Jun 25, 2019

jordanranz commented Jul 9, 2019

stale bot commented Aug 8, 2019

stale bot commented Aug 15, 2019

pwfcurry commented Sep 22, 2019 • edited

nihp commented Apr 29, 2020 • edited

sanyashvets commented May 8, 2020

nihp commented May 21, 2020

aleckzts commented May 30, 2020

gruckionvit commented Aug 13, 2020

github-actions bot commented Mar 30, 2022

gerrytsui commented Jun 19, 2019 •

edited

laurib commented Jun 19, 2019 •

edited

meetfilipe commented Jun 20, 2019 •

edited

adnan333bd commented Jun 24, 2019 •

edited

pwfcurry commented Sep 22, 2019 •

edited

nihp commented Apr 29, 2020 •

edited