aws-amplify / aws-amplify/amplify-ui-android

[Authenticator] Autofill assumes SMS OTP on code input view

Open
#286 1 comment 0 reactions 0 assignees View on GitHub
authenticator bug
Dominant language
Kotlin
Stars
25
Forks
18
Avg merge
7d 3h
Merged PRs (30d)
1

Description

### Before creating a new issue, please confirm:

- [x] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-ui-android/issues?q=is%3Aissue+).
- [x] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-ui-android/blob/main/CONTRIBUTING.md#reporting-bugsfeature-requests).

### Which UI component?

Authenticator

### Gradle script dependencies

```kotlin
// Put output below this line

```

### Environment information

```
# Put output below this line

```

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

_No response_

### Describe the bug

When the user reaches the OTP code entry view (e.g. during MFA or when confirming account signup) the autofill value is always set to `ContentType.SmsOtpCode`. This works great if the OTP code was sent via SMS but no so much if it was sent via email.

Autofill value should only be set if the delivery medium for the code is SMS. For Email codes there is no autofill support.

### Reproduction steps (if applicable)

_No response_

### Code Snippet

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

```

### Log output

```
// Put your logs below this line

```

### Configuration File

_No response_

### Additional information and screenshots

_No response_

Contributor guide

Open the contributing guide

Research direction

Start at the Authenticator OTP code entry view and trace where the autofill value is assigned as ContentType.SmsOtpCode. Verify the delivery medium before enabling SMS autofill, leave email codes without autofill support, and confirm both SMS and email code-entry flows behave as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.