I've never had that particular use case myself. Generally speaking, the decision to enable/disable happens during app init. Usually checking if this is a debug or release build, then simply not initializing Crashlytics in the former case. So, off hand, not sure. I'm not even sure if you can toggle that from the platform Crashlytics API, much less the CrashKiOS wrapper. Is there a specific use-case involved?