Say you have an existing app on the play store that's not enabled for Android Auto (no Android Auto metadata in the manifest, etc.), and you want to release a new version that is. When deploying the new release, Google Play warns you that the new build is compatible with fewer devices than the original.
So you decide to retain the previous binary as part of the new release. As in, the new release includes two APK's, one which includes Android Auto support and one which does not.
Could this configuration lead to the release being rejected when Google reviews it for Android Auto, or is their review process smart enough to ignore the APK that's not flagged as supporting Auto?
Specifically, I'm wondering is this kind of setup might lead to a vague/nonspecific rejection reason, like:
Your app does not perform all functions properly or as expected from a user perspective.