Instabug Pod Spec Modifies Project Files

[ltdowney]

I want to be able to use Instabug via Cocoapods, but this munging of my project files with your dSYM upload script is unacceptable. I appreciate the thought, but I can take care of marshaling my own build artifacts. Our continuous-integration server is completely hosed as a result of this change, and one of my colleagues is in the process of setting up a fork as I type this, which would've been completely avoidable if this... feature... had been optional.

[mzsoliman]

First let me apologize for the late reply.
I understand your frustration, but I hope that you understand why we've added it.

Anyway, we've just pushed a new update for the SDK that should fix this issue. The new upload script will not fail your build incase any error happened. You can still remove the build script if you want to.

Given the new build script, do you still think that the automation of adding the build script is annoying for you?

[mzsoliman]

I've also added a new branch that does the same as your PR, and I'll keep it updated with each SDK release.

Now you'll have to use the command that points to this branch while integrating the SDK. Here's it:
pod 'Instabug', :git => 'https://github.com/Instabug/Instabug-iOS', :branch => 'no_build_script'

[ltdowney]

Thanks for the update. I'll talk it over with my coworkers, but I think your two proposed solutions still don't quite get to where we'd want to be.

If you're dead set on imposing this build script phase on your users then I'd propose that you modify it to check for the presence of an env variable—say, INSTABUG_SKIP_UPLOAD_SCRIPT—and exit immediately if set.

[mzsoliman]

Why do you think that the other branch won't work for you? By using it the script won't even be added to your project!