Shaky skips the feedback form after the bottom sheet was dismissed
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Read the delegate's launchShakeBottomSheet, which sets isBottomSheetFlowActive = true, then onDataReady/doStartFeedbackFlow where the flag is only cleared after a submitted sheet flow, and the Dismiss row handler in the bottom sheet. Reproduce with the sample app: "Manually launch bottom sheet", "Dismiss", then "Manually start feedback". Done means the sheet's OnCancelListener clears the flag, the Dismiss row calls cancel(), flow-starting rows still call dismiss(), and the manual flow reaches FeedbackActivity.
Written by the indexing model from the issue text.
Description
On main (ca3e5f0), with the default delegate (shouldUseBottomSheet() returns true):
- Shake, or call
startShakeBottomSheetFlowManually(). The bottom sheet opens. - Close it without picking a row: tap "Dismiss", press back, tap outside or swipe it down.
- Call
shaky.startFeedbackFlow(), which the README suggests for starting the flow without a shake.
Expected: FeedbackActivity opens and the user can write a message.
Actual: after the screenshot is collected, delegate.submit() is called right away with no message and a null title. With EmailShakeDelegate that opens the mail app with only the screenshot attached.
launchShakeBottomSheet sets isBottomSheetFlowActive = true when it shows the sheet. The flag is only cleared in onDataReady after a sheet flow has submitted. If the sheet is closed without a choice, nothing clears it, so the next doStartFeedbackFlow() from startFeedbackFlow() takes the sheet branch in onDataReady. The sample app shows it too: tap "Manually launch bottom sheet", tap "Dismiss", then tap "Manually start feedback".
I have a small fix: clear the flag in an OnCancelListener on the sheet, and make the Dismiss row call cancel() instead of dismiss(). The row taps that start a flow still call dismiss(), so their path is unchanged. A plain dismiss listener would not work: the row tap broadcasts first and the dismiss callback would clear the flag before onDataReady reads it.
- Dominant language
- Java
- Stars
- 162
- Forks
- 59
- 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 linkedin/shaky-android
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
linkedin/shaky-android#60 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
linkedin/shaky-android#54 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
linkedin/shaky-android#48 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
linkedin/shaky-android#45 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
linkedin/shaky-android#20 · 1 reaction ·
All issues in linkedin/shaky-android
Similar issues
-
JPA security login throws when the stored password or roles string is nullPossibly taken @SebTardif claimed this today. Openarea/security env/windows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
quarkusio/quarkus#58548 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
marchof/java-almanac#354 ·
-
bug posit-ai
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuantConnect/IBAutomater#122 ·