-
Notifications
You must be signed in to change notification settings - Fork 4
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
Getting error while call authenticateWithCognitoIdentityPool #12
Comments
I have downgraded the dependency and changed the code accordingly. It's solved this crash. But now facing the Exception:
Code:
Dependencies:
I also noticed that my AWS account was configured with region 'ap-southeast-2' but the exception shows 'us-east-1'. Here is the reference link that I followed: https://docs.aws.amazon.com/location/latest/developerguide/dev-location-libraries.html#loc-sdk-auth-mobile-Android It would be great if anyone could help me to resolve this. |
Hello, let's see if we can help you resolve this issue. First a couple of follow up questions:
|
Hello @bridyck, Thanks for the reply!
I have downgraded both.
Here is the IAM role policy we are using.
Also, we have reviewed the reference link, which needs the API key to execute API. Is there any way to authenticate using cognito instead of using API keys? Please let me know if you need any other information. |
That IAM Role looks right. To answer your question, yes you should be able to authenticate using cognito instead of API Keys. One more sanity check - You have attached the IAM role policy to the IdentityPool correct? These steps are not Android SDK Specific, but they are in the steps for setting up the needed resources for any of our SDKs: https://docs.aws.amazon.com/location/latest/developerguide/authenticating-using-cognito.html |
I have already implemented Cognito in the app and now I'm going to implement the
SearchPlaceIndexForPosition
feature.I'm getting errors while calling
authenticateWithCognitoIdentityPool
.Here is the error:
Cognito Policies
Code
The text was updated successfully, but these errors were encountered: