Skip to content
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

AWSCognitoAuth SignIn error=Loading page failed #1003

Closed
ksenia834 opened this issue Jul 23, 2018 · 6 comments
Closed

AWSCognitoAuth SignIn error=Loading page failed #1003

ksenia834 opened this issue Jul 23, 2018 · 6 comments

Comments

@ksenia834
Copy link

To help us solve your problem better, please answer the following list of questions.

  • What service are you using?
    AWSCognitoAuth with SAML Identity Provider (Azure AD)

  • In what version of SDK are you facing the problem?
    AWSCognitoAuth - v.2.6.25
    AWSUserPoolsSignIn - v.2.6.25
    AWSAuthCore - v.2.6.25

  • Is the issue limited to Simulators / Actual Devices?
    Issue is reproducing on iOS Simulator and Actual Device

  • Can your problem be resolved if you bump to a higher version of SDK?
    This is already the latest release version of AWS and iOS SDKs

  • Is this problem related to specific iOS version?
    Issue is reproducing on iPhone 7 with iOS 11.3.1, iPad Pro iOS 11.4.1.
    I can't reproduce it on iPad with iOS 10.3.1, so not sure about version dependency.

  • How are you consuming the SDK? CocoaPods / Carthage / Prebuilt frameworks?
    With Cocoapods

  • Can you give us steps to reproduce with a minimal, complete, and verifiable example? Please include any specific network conditions that might be required to reproduce the problem.

Steps to reproduce:

  1. Login user with Azure AD account.
  2. Logout user.
  3. Wait few seconds: 0 - 60.
  4. Login again.

Actual result: Error Domain=com.amazon.cognito.AWSCognitoAuthErrorDomain Code=-2000 "(null)" UserInfo={error=Loading page failed}.
Expected result: Show SignIn Screen to the user.

Additional information:
AWSCognitoAuth methods used for sign-in:

first variant:
– getSession:completion:
– signOut:completion:

second variant:
– getSession:
– signOut:

Issue is regardless of which variant is used.

Issue is also reproducing on example project: https://github.com/awslabs/aws-sdk-ios-samples/tree/master/CognitoAuth-Sample/Objective-C/CognitoAuthSample with required AWS settings.

I also found that similar issue was already opened and closed without solving an error:
#857

Do you have any information what the reason of this problem and is it possible to solve this error on AWS SDK side?

Thanks!

@moisesrojasGL
Copy link

Hi @ksenia834 any luck on this? I have the same issue.

@ksenia834
Copy link
Author

ksenia834 commented Aug 7, 2018

Hi @moisesrojasGL, I still have this problem. It should be fixed on the framework side. Meanwhile, you can try workarounds from issue #857 or handle this error by code AWSCognitoAuthClientErrorLoadingPageFailed and implement some kind of retry functionality. If you've found better solution please write about it.

@moisesrojasGL
Copy link

Hi @ksenia834 I think the best solution is to implement ASWebAuthenticationSession in some sort of Swift Extension (or in a fork/branch from this SDK) since this is the right way to load web pages to handle one-time login (at least when using Google Sign-in, my case). I hope this be fixed by the AWS guys soon. Please see this and this.

PD: To any of the new visitors on this thread correct me if I'm lost or wrong. Any feedback or update will be appreciated. Thanks!

@dluquedavid
Copy link

dluquedavid commented Aug 17, 2018

problem only happen when yo set "identity_provider=google", the redirect fail.
a fix is here.
#857

@stale
Copy link

stale bot commented Sep 22, 2018

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 stale bot added the wontfix-stale label Sep 22, 2018
@stale
Copy link

stale bot commented Sep 29, 2018

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

@stale stale bot closed this as completed Sep 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants