Closed sima-11 closed 4 years ago
Hi @sima-11. Great question. Let me see if I can help track down an answer.
Stay tuned.
Hi @sima-11 . I spoke with my team to be sure, and by design, after the Apptentive.register(with:)
method has been called, the SDK cannot be disabled. It will continue to run until the app fully exits.
Can you tell me a bit more about why you're trying to disable the SDK? Though we don't support doing that, I may be able to offer help solving whatever problem you're trying to solve.
Thanks @CaseyApptentive. It's basically required by TCF 2.0, and we need to enable/disable the SDK at runtime, ideally without force quitting our app.
Thanks for the clarification @sima-11. Are you or your team also discussing this with Pat from Apptentive's Customer Success team? I work closely with him and want to be sure we're not crossing wires.
If it's okay with you and you are working with him, let's use that thread moving forward so everyone is on the same page.
Hi @CaseyApptentive, yes, I've also had some conversation with Pat, and he mentioned he'll have discussion with the team. 👍
Thanks, @sima-11. I'm going to close this issue for now to help keep discussion streamlined.
Dear team,
I couldn't seem to find a function to disable the framework once
Apptentive.register(with:)
is called. My assumption is if I pass in an invalid “configuration” parameter when calling “Apptentive.register(with:)”, it’ll probably disable the SDK? Would be helpful if you could provide some insight?Thanks!