-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Analytics Record [Unhandled promise rejection: Error: No credentials, applicationId or region #6145
Comments
I have gotten this same issue with trying to use analytics with auth, tried solutions from this thread (#3484) and disabling analytics fixes it, but I would like to find a real fix. |
I can confirm a similar issue still. It is a plain vanilla react-native expo application, using the exact steps prior to, and up to this step in the getting started guide:
|
@joebernard is seeing this also on |
Hopped on a call with @joebernard and @jpignata, @joebernard is checking if pinning specific versions of the analytics package will resolve his issue. |
+1 |
Resolving as this issue as a duplicate of the above related issue. |
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 |
Describe the bug
Analytics record function throws error:
[Unhandled promise rejection: Error: No credentials, applicationId or region]
......
.....
Expected behavior
Analytics logs record event without error.
Code Snippet
Analytics.record({name: 'profileVisit',attributes: { id: marker.id }});
What is Configured?
If applicable, please provide what is configured for Amplify CLI:
Auth, Storage (S3) and Analytics are configured.
aws-exports
file:};
Package.json
"@aws-amplify/analytics": "~3.2.1",
"@aws-amplify/api": "~3.1.9",
"@aws-amplify/auth": "~3.2.5",
"@aws-amplify/core": "~3.2.5",
"@aws-amplify/storage": "~3.2.0",
Using expo SDK 37, which uses react native 0.61
At the time of logging the analytics event, the user is authenticated with Auth.signIn().
The text was updated successfully, but these errors were encountered: