Two capture in a row leads to only latest one available

[pierroo]

bug report

I need to do two capture:
first one "as is"
then second one, after I hide some elements from the view, and then re-capture with removed elements

Both seems to be working, I get a local path as a result, HOWEVER once I try to use the first local path I keep getting the error:
"Can't request the image from the uri: file:///data/user/0/...blabla"

Whereas the latest is okay.

Version & Platform

react-native: 0.69.7
view-shot: 3.5.0

Tested on android only for now

[gre]

Temp file handling was changed in v4.0.0 and further improved in v5@alpha. Can you try npm install react-native-view-shot@alpha and let us know if this is resolved? Stable v5 coming soon.

[gre]

Hi @pierroo,

We think this is likely resolved in v5. The Android capture path has been substantially refactored across v5.0.0 / v5.0.1, in particular the bitmap lifecycle: PR #628 introduced a CAS-based handoff between the capture executor and the UI runnable so the canvas-backing bitmap can no longer be returned to the reuse pool while a previous capture is still using it — which matches the symptom you reported (the first URI becomes invalid as the second capture completes).

v5.0.0 + v5.0.1 are released and on npm now. Please give it a try and don't hesitate to open a fresh issue if you still see the same behaviour — with a minimal repro of the back-to-back captures, RN version, and view-shot version, we'll dig in.

Closing as likely fixed.

Release notes: https://github.com/gre/react-native-view-shot/releases/tag/v5.0.0