Don't Use This Package If Not Using CocoaPods For iOS

[DISKONEKTeD]

Do yourself a favor: don't use this package if you're not using cocoapods on iOS (though, I even saw issues with that).

It's a disservice to claim it works without it because it doesn't. It only works in the development phase. You're under the assumption that if you follow the instructions that it will work, but it won't. It's heavily documented many people can't get it to run in production. Search.

It works great otherwise, but I've completely wasted my time with it, unfortunately.

It's due to the prebuilt stuff that are included that are considered obsolete architecture under the eyes of Apple. They are included supposedly for simulator support, but it makes dealing with the package a headache on iOS otherwise if you want to use your app in an actual production environment.

I recommend just sticking to the original, even if limited: https://github.com/react-native-community/react-native-image-picker

cheers.

[superandrew213]

I have been using this package for over a year without cocoapods (and with cocoapods at the begining, since it was the only option).

I don't have any issue building and running it on sim and production.

[DISKONEKTeD]

I tried as instructed, in the latter portion and it's always the same error. I looked through various threads and all I see repeatedly people repeatedly dropping the package instead because they can't get it to run in production.

I only saw one potential solution ( #638 (comment) and you yourself had issue with it as well way back: #61 ), and it requires even more tedious instructions than mentioned in the readme page (which I rather just not deal with). It's ultimately misleading. I been working on an app for the past half year or so, and was using this only to find out I can't use it.

Then there are other issues that cropped up when i was trying to "fix" it for production like this one: #105

and I just had enough personally. I just wanted to let others know, since there doesn't seem any warning about the troubles people face with the manual installation.
The package works great otherwise, especially in development iOS and on android.

[krewllobster]

The installation instructions could certainly use some work and specificity for ios installation. I messed it up first because I couldn't find the framework files that the docs reference. However, the second time I looked, I found them, and was able to add them, then go and link the library in build phases and it worked fine.