It’s not used. @Pkeod’s suggestion should work fine. Adtruth is used for internal King games, which access it by calling in to a lua module called adtruth. (I think you can do something like pprint(adtruth) to inspect it.) It’s used mainly for tracking cross-promotion. The reason it’s not documented is that we were not really happy with that API, it should be generalized into something more widely usable. Adtruth basically does JS-invocation in a webview, and it seems like that could be usable for many other games, without tieing it to adtruth in particular.
The fact it’s not used and it being for internal use only is good by me. It is one less thing to consider
when worrying about user privacy.
Also, the contents of the file
\plugins\com.dynamo.cr.bob_1.0.0.201603150157\com\dynamo\bob\bundle\resources\android\AndroidManifest.com
look like a manifest template, which is then filled in during the packaging process. I assume that I could even specify my own manifest in the game.settings file or edit the template xml to suit my needs, but I’m not sure if that is a good/best practice.
You need to take care when you use your own manifest file and make sure to periodically check your own manifest file against the default manifest file. Some releases adds or changes features that also require changes to the manifest file (new permissions, minimum sdk version, activities etc)