-
Notifications
You must be signed in to change notification settings - Fork 255
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
If I touch and hold toast, it never hides #299
Comments
Yeah, also facing the same issue, touch and swipe lil bit down and hold then release, it never hides. And if you hold longer it hide and reappear when release the touch. |
@calintamas any update on this |
Facing the same issue here. |
same issue here |
any solution ? |
used this logic const {isVisible} = props; const [isVisibleToast, setisVisibleToast] = useState(false); useEffect(() => { return isVisibleToast ? ( |
Same issue here, toasts won't hide. I would say it's critical bug. |
I guess the reason is that after |
Any plans in fixing this? |
@calintamas Hi, do you have any updates on this? I've also encountered this bug on Android. Should I address it? |
The issue persists in 2024... |
Just applied a patch from my side that will prevent the 2nd non-closable toast message from being there. We'll be running some QA testing to check if it doesn't affect other features and then I can consider creating a Pull Request to fix that issue! EDIT Solution has been problematic when running QA regressions, I'll update a workaround here when finding an stable solution. |
node_modules/react-native-toast-message/lib/src/components/AnimatedContainer.d.ts add this:
|
Still it recreates a new instance media_20240723_101907_3362853197575039291.mp4 |
Not sure if it is intentional behavior, but if I touch and hold toast, it never hides (
autoHide
is set totrue
). The hiding animation takes place, but toast stays on screen infinitely. You may need to pull your finger down a bit after the hiding animation is complete in order to display toast again. I get this behavior on iOS as well as Android. Package version: 2.1.0Originally posted by @danieldaukapp in #280 (comment)
The text was updated successfully, but these errors were encountered: