can not readFile that captured as tmpfile

readFile() method of both “react-native-fs” and “rn-fetch-blob” works well for static asset files or the output of “react-native-camera” library. But the readFile() method can not read the file that captured via “react-native-view-shot” as tmpfile.

react-native@0.52.2 react-native-view-shot@2.3.0 react-native-fetch-blob@0.10.8 rn-fetch-blob@0.10.11 react-native-fs@2.10.14

class SomeComponent extends Component {
  async captureAndReadFile() {
    try {
      let filePath = await this.viewShot.capture() ;
      let data = await RNFS.readFile(filePath, 'base64');  // or RNFetchBlob.fs.readFile(filePath, 'base64');
      return data && new Buffer.from(data, 'base64'); 
    }
    catch(err) {
      console.warn(err);
    }
  }

  render() {
    return(
      <View>
        <ViewShot 
          ref={ref => this.viewShot = ref}
          options={{ format: 'jpg', quality: 0.8 }}
        />
        <Button title="Press" onPress={this.captureAndReadFile.bind(this)}
      </View>
    );
  }

Am I missing something ? Thanks in advance.

[serhiipalash]

Hi @gre ! I think this bug is still active.

Expo.takeSnapthosAsync has this bug in Expo 31 compare to Expo 30 (iOS tested). In Expo 31 takeSnapthosAsync was updated to use react-native-view-shot v2.5.0, and now takeSnapthosAsync result “tmpfile” uri is not compossible with Expo.MediaLibrary or Expo.FileSystem any more. That is because “tmpfile” uri path is in /private/var/... and Expo.MediaLibrary and Expo.FileSystem can only work with paths that are in public system scope /var/.... When you try to save taken view snapshot to user photos or temporary dir, you will see an error “Couldn’t read …”.

As I remember in Expo 30 version of react-native-view-shot was something around v1.1.0.

[gre]

I think this is fixed. I was properly able to get the data from file and render it back in https://github.com/gre/react-native-view-shot/commit/8a6ea61c300d4ee7cb4fae2b9eec28d3c0b95dfe

works on iOS and Android.

Please report back if you are still having an issue (writing an example to reproduce the bug is the best)