You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the Snackbar implementation, the Mobile Feature Support team reported that they needed to patch our useSnackbar hook for usage in the app. They specifically ran into issues when a Snackbar was shown, and then hidden due to navigation change. They mentioned that issue is likely because Snackbar was being called as part of a useEffect on one of the app screens and thus had to be included in the useEffect dependency array, and this caused some side effects without the memoization of useSnackbar
1/23/2025 - the deployment scheduled for 1/22/2025 was cancelled. Rolling this ticket to Sprint 10, for the next deployment (scheduled for 2/5/2025, go-live on 2/11/2025 in the App Stores)
Description
As part of the Snackbar implementation, the Mobile Feature Support team reported that they needed to patch our
useSnackbar
hook for usage in the app. They specifically ran into issues when a Snackbar was shown, and then hidden due to navigation change. They mentioned that issue is likely because Snackbar was being called as part of auseEffect
on one of the app screens and thus had to be included in theuseEffect
dependency array, and this caused some side effects without the memoization ofuseSnackbar
Acceptance Criteria
useSnackbar
if they make senseThe text was updated successfully, but these errors were encountered: