Tap action has an effect on the emulator by showing next screen. But the test timeouts.
This issue is similar to github issue https://github.com/wix/Detox/issues/1699
link : https://github.com/wix/Detox/issues/2652
The issue was with animation which blocks from going idle. Please take a look at the above issue.
Related
I was trying to implement a WhatsApp like cancelling recording button.
Everything was working fine, all animations lauching correctly, start and stop recording too.
But after a few seconds (could be 10 seconds or 1 minute) pressing the gesture handler, the app freeze, all animations start to lags and FPS drop to 0.
After trying many things, I found out that it is linked with a Flatlist I have in my view. When this Flatlist is inverted, that is when everything crash.
Here is the link of the Snack https://snack.expo.dev/#mikelh997/animationtest
Just try to move the mic for at least 30 seconds on a physical device and you will see the app freeze
I am doing my tests on Android emulator and on Samsung S21 Ultra. On iOS everything seems to work fine
Thinking it was may be my packages version, I started a new project and put inside my view only a Flatlist with text items and my PanGestureHandler. All packages are up to date, even though the behavior is the same. If I remove "inverted" from my Flatlist, everything work fine.
I also tried to use Animated.Flatlist but no change (actually it's worse because inverted in Animated.Flatlist is not working correctly)
I also tried to reproduce it on Snack Expo, on my phone it crashes.
I noticed also that it is not linked to PanGestureHandler or Reanimated, because if I just create an animation with React Animated (with Animated.timing), and loop it, it does the same.
Edit : it seems like it is happening only on Android 13
After research, it is linked to Android 13, more and more people are facing this issue.
Only solution I found on Github was here, it is the only way to make it worked while waiting for a fix
style={{transform: [{rotate: '180deg'}]}} seems to be the best workaround for the time being.
So ErrorBoundaries are a pretty cool thing and all,
but in Development, they show a red (dismissible) Error Screen by default which always needs to be dismissed, before the Fallback-Component is revealed.
This is fine since it doesn't happen in release builds, yet incredibly annoying for testing error states.
Is there a way to disable the red screen in React Native?
All suggested answers in this thread haven't worked for me.
Would be very thankful for any help!
Thanks a lot!
Using React-Native I can not block the screenshot. I need to block or blur the screen for IOs. I've tried several things but I could not. Does anyone have a solution?
i think this libary should be helping https://github.com/hawkup/react-native-prevent-screenshot
Currently the best method to do prevention in IOS is using https://screenshieldkit.com/
However, I created a lib to block screenshot (on android) and detect screenshot action on IOS.
https://www.npmjs.com/package/react-native-screenshot-prevention
Im using Appium to test my notifications in my iOS app.
Im sending with another device a notification while the iOS app is in BG. Then I swipe down using :
((IOSDriver) wd).swipe(500,0,500,1000,1000);
The above works, the screen get scrolled down and I can physically see the notification. The issue is that the appium still inspects the screen below.
I checked appium inspector and it verified that it doesn't recognize nothing but the elemnts of the layer below the notifications one.
Any approach ??
As long as I know it is known limitation for iOS now.
You can get notification bar elements on Android only
But based on top comment it should be possible to wrap up with Appium since Xcode 9 introduced interaction with multiple apps, so its matter of time.
I found a workaround that fits my needs.
I found out that if I click the home button and then swipe down the notification are visible to Appium.
Because Appium not having key events for iOS, iPhone has the an accessibility option for home button, I toggled that on and I can simply click it during the test and swipe down the notification center.
I know it's not ideal but its working.
Thanks for the help.
When I am running react native in xcode, my error screen is white. See screenshot. If I highlight one of the rows, I can then see the text. But this seems pretty odd. Any ideas what would have caused this? Wasnt always the case.
I recently had the same issue, and I used git bisect to find the commit where the problem was introduced. In my case I found that when we changed our launch screen from being a .XIB (LaunchScreen.xib) to a Storyboard (LaunchScreen.storyboard) it caused my error screen to look like yours, so reverting those changes fixed it for me.