aws-amplify / aws-amplify/amplify-android

Allow local signout to continue even if signout fails in hostedui webview

Open
#2,842 3 comments 2 reactions 0 assignees View on GitHub
auth feature-request
Dominant language
Java
Stars
287
Forks
132
Avg merge
2d 2h
Merged PRs (30d)
45

Description

### Before opening, please confirm:

- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-android/issues?q=is%3Aissue+) and [discussions](https://github.com/aws-amplify/amplify-android/discussions).

### Language and Async Model

Kotlin

### Amplify Categories

Authentication

### Gradle script dependencies

Not Relevant

### Environment information

Not Relevant

### Please include any relevant guides or documentation you're referencing

_No response_

### Describe the feature request

There have been a few asks to allow the device credentials to be cleared even if hostedui signout from the browser fails. This case is primarily if the device does not have network.

The reason this has not been allowed is because it leaves the user signed in on the browser. Launching `signInWithWebUi` again would end up automatically signing in without presenting a login screen in the browser, since the previous credentials are still present in the browser. We should check if there is any possible way to force the login screen when relaunching the flow.

### Initialization steps (if applicable)

_No response_

### Code Snippet

```java
// Put your code below this line.

```

### amplifyconfiguration.json

_No response_

### GraphQL Schema

```graphql
// Put your schema below this line

```

### Additional information and screenshots

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing the hostedui signout failure path and the signInWithWebUi relaunch flow described in the issue. Determine how local device credentials are cleared when browser signout fails and how the next login can force a login screen; done means the intended behavior is covered without silently reusing the browser session.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
authentication, mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.