Support asset-library / camera roll URLs #60
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
auser approved these changes Oct 11, 2016
| Was looking for this. Awesome! |
| @alexkendall just note that there's a subsequent PR #66 which hasn't yet been merged to fix permissions issues when deploying to a device. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Currently the library doesn't support iOS asset-library URLs which are what the RN CameraRoll integration supplies to you. This PR adds a check for the asset-library URL and then uses the iOS Photos library to make the image available to Firestack to then upload.
This is based off code given in one of Google's CodeLabs for Firebase: https://codelabs.developers.google.com/codelabs/firebase-ios-objc/index.html?index=..%2F..%2Findex#8