-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expense - On selecting a category/ tags by multiple tapping, user directed to conversation page #53344
Comments
Triggered auto assignment to @puneetlath ( |
Edited by proposal-police: This proposal was edited at 2024-11-30 21:59:49 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Expense - On selecting a category/ tags by multiple tapping, user directed to conversation page What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)
<View
ref={ref}
style={[styles.flex1, {minHeight}]}
// eslint-disable-next-line react/jsx-props-no-spreading, react-compiler/react-compiler
{...panResponder.panHandlers}
testID={testID}
pointerEvents={isFocused ? 'auto' : 'none'}
> App/src/components/ScreenWrapper.tsx Lines 262 to 268 in 3cc88f5
Result |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: V9. 0.69-0
Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
On selecting a category/ tags by multiple tapping, user must not be directed to conversation/merchant page instead of expense details page.
Actual Result:
On selecting a category/ tags by multiple tapping, user directed to conversation/merchant page instead of expense details page.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6680799_1732988031088.Screenrecorder-2024-11-30-22-56-36-735_compress_1.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: