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

Amplify V1 TIMEOUT for SignOut function #2933

Closed
1 task done
panqier opened this issue Sep 26, 2024 · 2 comments
Closed
1 task done

Amplify V1 TIMEOUT for SignOut function #2933

panqier opened this issue Sep 26, 2024 · 2 comments

Comments

@panqier
Copy link

panqier commented Sep 26, 2024

Before opening, please confirm:

Language and Async Model

Java

Amplify Categories

Authentication

Gradle script dependencies

implementation 'com.amplifyframework:core:1.38.8'
implementation 'com.amplifyframework:aws-auth-cognito:1.38.8'

Environment information

Put output below this line

Gradle plugin version 7.1.2
Gradle version 7.2

Please include any relevant guides or documentation you're referencing

#2218

Describe the bug

I have exactly same issue with this ticket https://github.com/aws-amplify/amplify-android/issues/2218
I saw the issue closed but not been given a solution.

I was trying to jumping amplify version from 1.2.0 to 1.38.8 which is the latest amplify v1 version. I am upgrading this because sign in is completely not working in API 34 devices.
So the upgrading will make the sign in works, but for sign out I am getting time-out.
I have followed the instruction to use HostedUIRedirectActivity in AndroidManifest and uncomment Amplify.Auth.handleWebUISignInResponse(data)

Suggestion?
fyi: this is old project not considering to migrate amplify v2 for now

Reproduction steps (if applicable)

call the signout function
user be redirected to signout web
keeping loading
after a few seconds webview closed

Code Snippet

// Put your code below this line.
        <activity
            android:name="com.amplifyframework.auth.cognito.activities.HostedUIRedirectActivity"
            android:exported="true">
            <intent-filter>
                <action android:name="android.intent.action.VIEW" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />

                <data android:scheme="@string/app_shcema" />
            </intent-filter>
        </activity>
        <activity
            android:name="com.aircanada.flightpass.ui.screens.BaseNavigationActivity"
            android:exported="true"
            android:screenOrientation="portrait"
            android:launchMode="singleInstance"
            android:windowSoftInputMode="adjustNothing">
            <intent-filter>
                <action android:name="android.intent.action.VIEW" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />
                <data android:scheme="@string/app_shcema"
                    android:host="signout"
                   />

            </intent-filter>
        </activity>

Log output

// Put your logs below this line


amplifyconfiguration.json

No response

GraphQL Schema

// Put your schema below this line

Additional information and screenshots

No response

@github-actions github-actions bot added pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Sep 26, 2024
@ruisebas
Copy link
Member

Hi @panqier, thanks for reaching out.

Please note that Amplify Android v1 is deprecated as of June 1st, 2024. As such, no new features or bug fixes will be added.

@ruisebas ruisebas closed this as not planned Won't fix, can't repro, duplicate, stale Sep 26, 2024
@github-actions github-actions bot removed pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Sep 26, 2024
Copy link
Contributor

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

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

2 participants