@oleg-derevenetz it does seem that the rule could be enhanced to allow no permissions on activities with the action of android.intent.action.MAIN defined. Seems like a good idea to have this check sense that’s how MAIN is intended to be used. That being said defining the permission as empty string resolves the issues and explicitly shows your intent that there are no permissions needed to launch this activity.
. . .
@G00fY2 one might argue that an application with multiple entry points is hard to secure and this check gives you pause to consider this. Of course it could very well be that your application’s use case is to have multiple entry points (more power to ya), in that case see above.
The solution above is arguably hackey, but it is explicit.