Fixed iOS Podfile

2023-10-10T12:12:15Z

Fixed iOS Podfile

Android SDK 33 update

2023-10-10T09:02:16Z

Android SDK 33 update

Internal Patch release

2020-08-09T06:25:46Z

Internal Patch release where the rn-fetch-blob is replaced with react-native-fetch-blob as there were few issues related to file access in IPhone devices while using RELEASE_TARGET.
The patch was added on the official tag v6.2.0.

v0.10.9: Fix for #467 (#472)

2017-08-09T09:56:39Z

bump to 0.10.8
Update PULL_REQUEST_TEMPLATE
Fix wkh237#468 "Messy error returns: Sometimes a string, sometimes an Error object"
Cleanup: remove an unused constant and duplicate method definitions
Cleanup:

fix minor errors in JSDoc comments, for example {string]} => {string}
fix parameter name "encode" => "encoding" (more logical, and it says so in the function's JSDoc too)
json-stream.js: split a looooong log message string constant into two parts and fix a typo ("maually"), and the type for objects is "Object" (capitalized) in Flow type annotations

Fix a (Flow) type conflict - fixes issue wkh237#461
NEEDS REVIEW - Attempt to fix some of issue wkh237#460 (Error message normalization)

Error messages reported by iOS and Android versions should be as similar as possible. Also, within the same system there should be consistency. This patch is an attempt to bring a LITTLE more of this consistency to the error messages. I also fixed some very few minor language issues, like "does not exist" (is the correct English). I tried keeping the changes to a minimum.

Background: In my project code I want to know when a file already exists (e.g. after calling fs.createFile), and the only way is to check the error message string that I get. It's bad if they differ between versions (createFileASCII and createFile) and then also between Android and iOS version. At least some core part of the string should be the same, so that I have something to match.

Ideally messages should come from a centralized easy (easier) to maintain file (for both iOS and Android), and ideally both systems should have the same errors and messages as far as possible.

Fixes wkh237#467 by improving the write() function of write streams: By resolving with the RNFetchBlobWriteStream instance instead of with "undefined" writes can now be chained:

RNFetchBlob.fs.writeStream(PATH_TO_FILE, 'utf8', true)
.then((ofstream) => ofstream.write('foo'))
.then((ofstream) => ofstream.write('bar'))
.then((ofstream) => ofstream.write('foobar'))
.then((ofstream) => ofstream.close())

Reference: wkh237#467 (comment)

v0.10.8

2017-08-03T01:37:08Z

bump to 0.10.8

v0.10.7

2017-08-02T15:04:09Z

Merge branch '0.10.7' of github.com:wkh237/react-native-fetch-blob in…

v0.10.6

2017-06-26T15:52:27Z

bump to 0.10.6 and update contributors

v0.10.5

2017-04-26T09:31:06Z

Catch null contentUri (wkh237#343)

v0.10.4

2017-03-31T02:14:23Z

bump to 0.10.4

v0.10.3-beta.1

2017-02-05T03:38:05Z

bump to 0.10.3-beta.1

Release notes from react-native-fetch-blob

Fixed iOS Podfile

Android SDK 33 update

Internal Patch release

v0.10.9: Fix for #467 (#472)

v0.10.8

v0.10.7

v0.10.6

v0.10.5

v0.10.4

v0.10.3-beta.1