iOS: Device name has already been used by this user
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I downloaded the iOS app to give it a try, and followed these steps:
- Selected login
- Input username
- Chose to authenticate via password
- Added new device name
- Realized that by accepting my keyboard's autocorrect, the capitalization just entered was not consistent with my other device names
- Viewed list of devices and deleted the device I just added (for my iPhone)
- Was logged out
- Confirmed removal of device (using my laptop browser)
- Deleted the app and re-downloaded
- Repeated steps 1–4, but used the capitalization I wanted
- Was shown this view (the progress circle just keeps spinning and the Log in button is never selectable no matter what I choose in the above dropdown and text inputs):

I couldn't find any reference to restrictions on reuse of device names in the documentation, or any mention of case-insensitivity. If this is not a bug, then I think it should noted that "YOU CAN'T REUSE A DEVICE NAME EVEN IF YOU CHANGE THE LETTER CASE" at the time of device name entry.
What's going on here? Bug? UX oversight? Other?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the iOS login flow using a device name, delete that device, and retry with capitalization changed. Check the device-name reuse behavior and the non-selectable Log in state; done means the intended behavior is established and either the login flow works or the restriction is clearly communicated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100