tag-edit-playing.yaml: keyboard hides the tag editor's Save button, so tag-edit-queued fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- mobile-dev, testing-qa
Research direction
Run support/scripts/emu-verify.sh --check tag-edit-queued and inspect support/maestro/tag-edit-playing.yaml at the failing Save step. Compare tag-edit-not-playing.yaml and shell-tag-editor.yaml for the same keyboard behavior, then verify the edited title assertion and rerun the affected flow until Save is visible and the check passes.
Written by the indexing model from the issue text.
Description
support/scripts/emu-verify.sh --check tag-edit-queued on main 73d5e4831 gets through setup_taglib_provider (librarySongCount 5, playlists 2), then fails in support/maestro/tag-edit-playing.yaml at tapOn: "Save".
Screenshot at the failing step: the soft keyboard is up after inputText and covers the Edit Tags dialog's bottom (Save isn't on screen). Also, the keyboard auto-capitalised the typed text to "Taglib One (Edited)", while the flow types "(edited)", so any later exact-title assertion would miss even once Save is reached.
Likely fix: - hideKeyboard before tapping Save (and check tag-edit-not-playing.yaml / shell-tag-editor.yaml for the same pattern), and match the edited title case-insensitively, or type text the keyboard won't recapitalise.
Found while verifying #428.
- Dominant language
- Kotlin
- Stars
- 228
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from timusus/Shuttle2
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
All issues in timusus/Shuttle2
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
detekt/detekt#9761 · 1 comment · 2 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
yschimke/compose-preview-server#1163 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
T31n/YagniLauncher#1051 ·
Maintainers usually reply within 1 day
-
Accepted Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ankidroid/Anki-Android#22114 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day