-
Notifications
You must be signed in to change notification settings - Fork 4
Sentry breaking the build #3
Comments
I added a |
It installed |
It's because our build toolchain now contains Swift, we have to use a specific build of Xcode now. Making sure travis is running on Xcode 8.3 conceptually fixed this, but the build failed due to the pod resource script which feels really weird = https://travis-ci.org/artsy/emission-nebula/builds/236080641 |
These issues look like they're covered in https://docs.travis-ci.com/user/common-build-problems/#Mac%3A-macOS-Sierra-(10.12)-Code-Signing-Errors |
Shame, I'll have to do all this then 3.0 will come out and it'll all be for nothing - getsentry/sentry-cocoa#154 |
Also tried: artsy/emission#572 |
Came to the conclusion on an airplane that I can override the Pod at our app level to just provide a fake API which we use, and we can use that to avoid all these swift issues |
Now using libraries again, shipped a few releases manually. I can archive correctly in Xcode, but struggling to do it right inside Fastlane |
So, the later issues around empty archives are fixed with 705a32d |
Seeing getsentry/sentry-react-native#32
Since we got Sentry + RN set up, builds are failing
The text was updated successfully, but these errors were encountered: