Pierre
Pierre
@songxiaoliang yup, not a sexy fix but I simply wrapped the capture in a 300ms timeout and it fixed it. no clue why, let me know if it worked for...
Not sure if it's related, but I'm getting that same error "getRectForRef" on android when handling popover visibility through state rather than ref.
> Try setting the useNativeDriver to false for the animations and see if it changes anything. Like this: > > ``` > animationConfig={{ > duration: 70, > useNativeDriver: false, >...
Using v1.3.2, this deprecated warning on componentWillReceiveProps still appears; Is there any fix planned for this? Thank you,
not stale; still happening.
Just passing by to thank you @gaelhuot , that was really helpful! Since this one is no longer maintained, at least I can patch-package the change you provided.
FYI the info still persists on v8.2.1 @MikhailSuendukov ; as a matter of fact I just created an issue on it (which I will close now that I found this...
I am not using any toast, but yes I can confirm @davidgvf issue: a full screen opac seems to be covering the screen when I use blurview (even if that...
if that matters, useTexture is also raising the same issue in latest version 9.108.3 (in dev mode only, the red warning leaves in production but that remains scary)
Hi @tiago-yoneda , I am also facing the same issue. It is completely random, only on production build, and not for every users. How do you downgrade to version 2.5.0?...