Just a question. Is it possible to remove the MCInitContentProvider in our AndroidManifest? Not have it registered when compiling the apk. It seems like the point of this content provider is to expose the context for the SDK. But during initialization, I've always passed in my own context. I can't determine the usage since the marketingcloud android sdk is obfuscated.

    tools:node="remove" />

1 Answer 1


The intention is not to expose Context to the SDK and it is not okay to remove this.

  • Thanks for answering! Though I think my team is passing the context to the SDK during the init function. is there MCInitContentProvider usages in the sdk other than registering in the AndroidManifest?
    – watts_up
    Apr 19, 2021 at 15:09
  • My security team flagged the content provider as a potential issue due to content provider being leaked to malicious third party apps (though it was patched 2 years ago, some devices might not be patched yet). I know this content provider is a very bare bones. I wonder if removing this content provider affect the sdk in any way.
    – watts_up
    Apr 19, 2021 at 16:22
  • Please see my answer. Do not remove the Content Provider.
    – Bill Mote
    Apr 19, 2021 at 18:08

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .