fix: Ensure we're referencing up-to-date swipe state when configuring interaction enabled #595
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For https://block.atlassian.net/browse/UI-9091
This resolves an issue where a cell would not respond to taps after the "full swipe" swipe action trigger.
The issue was that we were referencing stale swipe state when configuring
isUserInteractionEnabled
. It was quite unintuitive when debugging this, but the lineswipeState = state
immediately resulted in those variables holding different values while processing the swipe action 🙃. We would incorrectly fall into the.willPerformFirstActionAutomatically
case, making the content view unresponsive, despite theswipeState
reporting as.closed
.The SwipeActionsViewController has also been updated to demonstrate this is now working as expected.
Checklist
Please do the following before merging:
Main
section.