v2.21.0-alpha.5

Changes in v2.21.0-alpha.5

• [#10] Android: Patches a number of functions to correctly close file streams they open, thus preventing leakage of resources.
• Updates dependencies.

---

The aim for upcoming v2.21.0 release is to bring the previous latest react-native-fs v2.20.0 up to the standards of the latest React Native v0.72.x, without breaking API changes, with support of the new RN architecture, with backward compatibility to the old RN architecture, and on all supported platforms: Android, iOS, macOS (Catalyst), Windows. Also documentation revision.

As of v2.21.0-alpha.5:

• The core library setup and the code base as a whole have been refactored for RN v0.72.x standards.
• The following pieces of the library have been tested to work correctly (no warranty that no bugs have been missed) on all supported platforms:
  • All path constants.
  • These selected functions: copyFile(), copyFileAssets(), copyFolder(), downloadFile(), exists(), existsAssets(), getFSInfo(), mkdir(), moveFile(), read(), readdir(), readDir(), readDirAssets(), readFile(), readFileAssets(), stat(), unlink(), uploadFiles(), writeFile().
  • The rest of functions may or may not work.
• Added some new functions: pickFile().
• Misc non-breaking fixes in the existing functions.

v2.21.0-alpha.4

Changes in v2.21.0-alpha.4

• [#3] These functions have been verified and patched to work on all platforms they used to work in the original library: copyFolder(), downloadFile(), uploadFiles().

  BEWARE: For downloadFile() and uploadFiles() only the base functionality have been tested, no guarantees that all options work correctly on all platforms and RN (old/new) architectures.

• [#7] Declares React Native v0.72.x as required peer dependency.

• [#9] iOS: Corrects declared target iOS platform version to match that of RN (currently v13.4).

• Adds pickFile() function (as of now, it is implemented for Android and iOS only). It prompts user to select a file, using a platform provided file picker UI, and also allowing to access files outside the application sandbox (i.e. files outside the app sandbox aren't visible to other functions in the library directly, but pickFile() returns special security-scoped URIs for user selected files, which then can be used to access those files by other functions in the library).

---

The aim for upcoming v2.21.0 release is to bring the previous latest react-native-fs v2.20.0 up to the standards of the latest React Native v0.72.x, without breaking API changes, with support of the new RN architecture, with backward compatibility to the old RN architecture, and on all supported platforms: Android, iOS, macOS (Catalyst), Windows. Also documentation revision.

As of v2.21.0-alpha.4:

• The core library setup and the code base as a whole have been refactored for RN v0.72.x standards.
• The following pieces of the library have been tested to work correctly (no warranty that no bugs have been missed) on all supported platforms:
  • All path constants.
  • These selected functions: copyFile(), copyFileAssets(), copyFolder(), downloadFile(), exists(), existsAssets(), getFSInfo(), mkdir(), moveFile(), read(), readdir(), readDir(), readDirAssets(), readFile(), readFileAssets(), stat(), unlink(), uploadFiles(), writeFile().
  • The rest of functions may or may not work.

v2.21.0-alpha.3

Changes in v2.21.0-alpha.3

• These functions have been verified and patched to work on all platforms: copyFile(), getFSInfo(), moveFile(), read(), readdir(), readDir(), stat().
• Android: Patches the handling of path-to-URI transformation, which is used in several functions — Thanks to PR #6 by @IanOpenSpace

---

The aim for upcoming v2.21.0 release is to bring the previous latest react-native-fs v2.20.0 up to the standards of the latest React Native v0.72.x, without breaking API changes, with support of the new RN architecture, with backward compatibility to the old RN architecture, and on all supported platforms: Android, iOS, macOS (Catalyst), Windows. Also documentation revision.

As of v2.21.0-alpha.3:

• The core library setup and the code base as a whole have been refactored for RN v0.72.x standards.
• The following pieces of the library have been tested to work correctly (no warranty that no bugs have been missed) on all supported platforms:
  • All path constants.
  • These selected functions: copyFile(), copyFileAssets(), exists(), existsAssets(), getFSInfo(), mkdir(), moveFile(), read(), readdir(), readDir(), readDirAssets(), readFile(), readFileAssets(), stat(), unlink(), writeFile().
  • The rest of functions may or may not work.

v2.21.0-alpha.2

Changes in v2.21.0-alpha.2

• [#2] iOS: Fixes Old Architecture builds.

---

The aim for upcoming v2.21.0 release is to bring the previous latest react-native-fs v2.20.0 up to the standards of the latest React Native v0.72.x, without breaking API changes, with support of the new RN architecture, with backward compatibility to the old RN architecture, and on all supported platforms: Android, iOS, macOS (Catalyst), Windows. Also documentation revision.

As of v2.21.0-alpha.2:

• The core library setup and the code base as a whole have been refactored for RN v0.72.x standards.
• The following pieces of the library have been tested to work correctly (no warranty that no bugs have been missed) on all supported platforms:
  • All path constants.
  • These selected functions: copyFileAssets(), exists(), existsAssets(), mkdir(), readDirAssets(), readFile(), readFileAssets(), unlink(), writeFile().
  • The rest of functions may or may not work.

v2.21.0-alpha.1

The aim for upcoming v2.21.0 release is to bring the previous latest react-native-fs v2.20.0 up to the standards of the latest React Native v0.72.x, without breaking API changes, with support of the new RN architecture, with backward compatibility to the old RN architecture, and on all supported platforms: Android, iOS, macOS (Catalyst), Windows. Also documentation revision.

As of this v2.21.0-alpha.1:

• The core library setup and the code base as a whole have been refactored for RN v0.72.x standards.
• The following pieces of the library have been tested to work correctly (no warranty that no bugs have been missed) on all supported platforms:
  • All path constants.
  • These selected functions: copyFileAssets(), exists(), existsAssets(), mkdir(), readDirAssets(), readFile(), readFileAssets().
  • The rest of functions may or may not work.