-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
When I navigate to a new screen in the stack, it sets an opacity color on this screen until it gets focus for example with an input #1796
Comments
Hi @davidgvf, would you mind posting a reproduction? |
I detect, that problem ocurring when install @stripe/stripe-react-native @kkafar Version updated |
Does that mean that the problem is resolved? |
The problem continues XD, but I have only realized that it conflicts with this library @kkafar and only in android |
Ok, I'm awaiting for requested reproduction. |
Is it okay if I upload a video here? @kkafar |
It would not help much. Please see this article. |
@kkafar @davidgvf we had seen similar opacity issue and without stripe. I tried reproducing but was unsuccessful. I'll try again. It gets resolved when i changed the default fade animation type for android. showtime-xyz/showtime-frontend#2213 |
This is not stale |
Just ran into this multiple times today. Sometimes, it even keeps the opacity at 0, even after the screen transition was finished. Only way to prevent this for us is to set animationDuration to undefined for android. |
In which section have you set the animation duration to 0?
El El vie, 14 jul 2023 a las 12:02, Hirbod ***@***.***>
escribió:
… Just ran into this multiple times today. Sometimes, it even keeps the
opacity on 0, even after the screen transition was finished. Only way to
prevent this for us is to set animationDuration to undefined for android.
—
Reply to this email directly, view it on GitHub
<#1796 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO4IC7CQEK2FLB7P6JT375LXQEKMTANCNFSM6AAAAAAZLYTUUI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Not 0, just undefined. The only way we could workaround was like so: <Stack.Screen
name="comments"
options={{
headerTitle: "Comments",
animation: Platform.OS === "android" ? "fade_from_bottom" : "simple_push",
animationDuration: Platform.OS === "android" ? undefined : 200,
}}
component={CommentsScreen}
/> |
Hi, i detect the problem in my case, if you have lib @react-native-community/blur, If you use the excessive style for the blurview, and you do not remove that component, that is, it is always rendered, in my case I used it for the toast notifications, the navigation behaves strange, putting screens in white or in x color |
@davidgvf Could you please elaborate your statement? We also use |
@simonbothen-radinn If you use blurview on android on any screen, this will cause those animation failures or making the screen blank, unless you remove it when you go to browse, it is if it remains active while browsing |
This workaround did it in my case + i had to add @hirbod Thanks dude My case (sometimes it works sometimes it doesn't) (S21Fe Android 13) Screen_Recording_20240130_114707_Expo.Go.mp4 |
Description
When I navigate to a new screen in the stack, it sets an opacity color on this screen until it gets focus for example with an input
Steps to reproduce
Snack or a link to a repository
s
Screens version
3.21.0
React Native version
0.71.11
Platforms
Android
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
Android emulator
Device model
pixel 3
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: