IssueTracker

When publishing a new version of my app with updated dependencies (no actual change in app functionality) my apps are repeatedly rejected. The message is:

No Auto functionality

The app did not appear in the Auto screen or lens picker when we attempted to test functionality.

• For example, your app does not contain an Intent filter for action "android.media.action.MEDIA_PLAY_FROM_SEARCH".

So there are two suggestions for what the problem is. The trouble is, neither of them are true:

1. The app did not appear in the Auto screen or lens picker when we attempted to test functionality.

This is incorrect, as can be seen in this screenshot:

Android Auto screen

My app is "Astiga" - it can be seen both in the picker, and the running apps.

1. • For example, your app does not contain an Intent filter for action "android.media.action.MEDIA_PLAY_FROM_SEARCH".

It does contain this intent filter. Here's a portion of my AndroidManifest.xml:

<intent-filter>
    <action android:name="android.media.action.MEDIA_PLAY_FROM_SEARCH" />
    <category android:name="android.intent.category.DEFAULT" />
</intent-filter>

So both suggested problems are incorrect.

I have followed up in appeal for more information about what is going wrong, and this was the response:

As much as I'd like to help, I’m not able to provide any more detail or a better answer to your question. In our previous email, I made sure to include all the information available to me.

I don't think this is useful. If an app review is rejecting a bundle, a description of what is wrong should be provided.

Right now I'm stuck with not being able to publish an app, and the clock is ticking on the target API requirement soon to be enforced.