TeamAmaze / TeamAmaze/AmazeFileManager
Allowing SMB connections with identical names leads to confusion
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Describe the bug
The menu displays multiple SMB Connection entries without any differentiation, making it difficult to identify distinct connections and potentially causing confusion.
To Reproduce
- Click the ‘+’ icon.
- Click ‘Cloud Connection’.
- Select ‘SMB Connection’.
- Click ‘USE CUSTOM IP’.
- Enter a server IP address in the ‘Server IP Address’ field (e.g.,
test.com). - Click ‘CREATE’.
- Repeat steps 1-6 using the same ‘Connection name’ (e.g., the default ‘SMB Connection’) but a different server IP address.
- Click the ‘Hamburger’ icon to view the connection list.
Expected behavior
Each SMB connection entry should display a unique or distinguishable ‘Connection name’ to help differentiate between distinct connections.
Screenshots
Smartphone (please complete the following information):
- Device: [Google Pixel 5]
- OS: [Android 14]
- Rooted: [No]
- Version: [3.10]
Contributor guide
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 issue through the SMB Connection creation flow, using identical connection names with different server IP addresses, then inspect the connection list opened by the Hamburger icon. Trace how SMB entries are labeled and make the entries distinguishable; done means separate connections no longer appear identical in the menu.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100