Closed dingbat closed 3 years ago
I'm actually now realizing maybe you do want this on a debug build running on the device, in case you are playing with the development version untethered and get a crash, so this may not be the best solution. Let me know.
I'm actually now realizing maybe you do want this on a debug build running on the device, in case you are playing with the development version untethered and get a crash, so this may not be the best solution. Let me know.
No, you're right, crash reporting is not something I regularly want. It's just that up until now I never had the need to disable it because I, of course, own the GoogleService-Info.plist
file. You're the first contributor, so you have the dubious honor of finding all the obstacles I built into the project 🙂.
Instead of defining a new preprocessor macro, could you please use the already existing macro LITTLEGO_NDEBUG
? This is defined in all configurations except in debug builds, so setupCrashReporting
should use
#ifdef LITTLEGO_NDEBUG
If I ever need crash reporting in a debug build I will fiddle with the project until I get it running.
DEBUG
compiler flag for use in debug builds only (note we can do something similar forRELEASE
)GoogleService-Info.plist
in debug builds making the project buildable from scratch (got an error about that file missing otherwise)setupCrashReporting
in debug mode