Anselmus K A Kurniawan
Anselmus K A Kurniawan
Update your `use-back-button-handler.tsx` with this, got it from [here](https://github.com/facebook/react-native/issues/3223#issuecomment-355064410) ``` import { useEffect, useRef, useState } from "react" import { BackHandler, DeviceEventEmitter } from "react-native" import { NavigationContainerRef } from...
Warning using my solution, it will remove all `hardwareBackPress` event listener from other libs too. correct way to handle back button in react navigation 5 is https://reactnavigation.org/docs/custom-android-back-button-handling but I'm still...
I created separate issue #357 because it's not relevant with this issue
Nope, as I said, I end up using `useSafeAreaInsets` and avoiding `SafeAreaView` as much as I can because of this performance issue
luckily for me, my current implementation doesn't give me any flickers, and when I check using logs, insets stay the same all the time (my app only use portrait orientation)...
I encounter this problem too, our PHP server rejected timezone from `moment.tz.names()`, either do something with the server code or is there any way ini moment to not return legacy...
There are a lot of factors that Google PageSpeed uses to determine your page speed and some of it doesn't really relate to RBP. So, to get a 100/100 rating,...
I think it is expected, you have to implement persisting state your self (eg, using local storage)
Still waiting for v5 release date :)
Hi guys, got the same issue but in my case, it only happens if I type fast enough (faster than normal typing), here is my code ``` import React from...