Swift Package Manager (new)
- React Native 0.87 can autolink the library through Swift Package Manager. The package ships a
Package.swiftwith three single-language targets, and an Objective-C protocol seam between the adapter and the Swift core, so the adapter no longer needs Swift's generated header. CocoaPods is unchanged (supersedes #496) - A CI job builds a React Native 0.87 app with SwiftPM autolinking next to the three CocoaPods linkages
- The podspec's public headers are the React-free leaf
ios/ReactNativeBlobUtilObjC/; the file transformer and exception-catch headers live there now, and the imports apps use are unchanged
Requests
- Android: a
fileCacheorpathdownload no longer rejects with "Unexpected FileStorage response file" when the app has an OkHttp application interceptor that wraps the response body (#494) autoandbinaryContentTypesare declared and documented, and so is theRNFB-Responserequest header. Afalseautois no longer sent; iOS read the key's presence, not its value- Android: under
auto, every response that is not text or JSON is written to a file, as on iOS. It used to file only a type listed inbinaryContentTypes
API
media.addDownloadtakesnotification, like the DownloadManager config;showNotificationstill works and warns onceURIUtil.isFileURIandURIUtil.unwrapFileURIrecognise theReactNativeBlobUtil-content://prefix thatwrap()gives a content URI- The Flow types exported from
index.jsmatchindex.d.tsagain (thetransform,androidandiosconfig keys,auto,binaryContentTypes, the response info), and a test keeps the two in step
Docs
- The wiki describes the 1.0 API, with diagrams; the 0.x pages stay, marked as such
Closes #365: a content:// URI is opened through its provider since 1.0, and the content prefix is now recognised everywhere in JavaScript too.