Can't run any of the sample in Android Device or Automotive emulator

[Swati90]

[mani-apps]

Yup same problem here I reported in this issue #16, anyone can help us? They have updated last week to implementation "androidx.car.app:app-automotive:1.1.0-alpha01" and "androidx.car.app:app:1.1.0-alpha01" and I think the README file is not up to date here? not really sure how to run it now, can find any documentation on it either since it's all really recent.

[Greathyx]

Same here. I am using Android Studio 2.4.1, but I still got the problem.

[mani-apps]

@kokoro-team @yjm607 can someone help us with this? using 4.2.1 too

[ikbalkaya]

Same here

[SamuelBrucksch]

Try version 1.0.0 instead of 1.1.0-alpha01 or enable beta in playstore for android auto.

[derjohng]

Same here. And, I got the error message as below. E/CarApp.Act: No handlers found for intent: Intent { act=android.car.template.host.RendererService }

[mani-apps]

From what I understood (and Google added to the readme) they released this new way of building automotive apps using Screens/templates but then they don't have a public Host to render these templates available yet.

Basically, the new automotive apps based on Screens/Templates (instead of activities/fragments) will not run on android automotive emulators for god knows how long? Find this really weird, how do we test the apps then?

Would be good if someone from Google Automotive team would help us, or reply to any issues 🤔

[blad]

This comment is not a solution to running apps on the Android Automotive OS Emulators. I ran into the same issue noted above, running the app in the emulator yields a message to update.

If one is trying to get the apps to simply run, the way forward is to use the Desktop Head Unit(DHU).

• Install the DHU
• Run the DHU
• Build and Install the App via Studio or CLI
• App should show up on the DHU. If it does not show then stop the DHU and start the DHU again, I've noticed that installing a new app does not automatically refresh the DHU.

[vy12021]

There have a new different error when running the sample app on the latest AAOS emulator (api level 31 reversion 2), as below is the error logs: CarApp.Act: Host service ComponentInfo{com.google.android.apps.automotive.templates.host/com.google.android.apps.automotive.templates.host.stub.ServiceStub} rejected the binding request

the error screenshot is still the top issue presented.

the error on the aaos for API level 31 reversion 1 as below: E/CarApp.Act: No handlers found for intent: Intent { act=android.car.template.host.RendererService }

so, I guess that the render service has been implemented on the latest AAOS build, but something is still wrong, really need the aaos team for help currently.

[vy12021]

The sample app works on the AAOS after updating the Host App to the latest via the Play store, You can try the README file section for details: Run the Automotive Apps in the Automotive OS Emulator, special the update guide.