5

I have an app with a CallKit call blocking extension. Generally it works fine, but on some devices it occasionally becomes disabled by itself (well, in fact by iOS I guess) after a while – so user has to go to Settings and re-enable it again manually. However, there is no any visible reason for such behavior: the volume of blocked phone numbers data is small enough (the app works even with larger datasets most of the time, so it shouldn't be a memory issue), numbers are sorted in a right order (ascending), there are no duplicated numbers etc. It is also quite hard to reproduce the problem. It feels like something from "outer world" interferes with the extension (another app with extension?), but there are no proofs.

What may be the reason of such auto-disabling and how to avoid that?

Any help would be appreciated.

Thanks!

degapps
  • 794
  • 5
  • 10
  • is the issue with iOS 13? – Sharad Paghadal Aug 03 '19 at 21:07
  • 1
    @SharadPaghadal Nope, it happens on 12.x (last noticed on 12.4). – degapps Aug 04 '19 at 11:13
  • Have you tried setting up crash logs on a test device? Something like crashlytics might help – Julian Silvestri Sep 06 '19 at 12:45
  • 1
    @JulianSilvestri Yes, but there's no any valuable info regarding the problem. In fact the issue has nothing to do with crashes – the app (and extension) works fine, just one day the toggle in Settings gets "off" status, and the app reports that the extension is disabled. – degapps Sep 06 '19 at 13:08

0 Answers0