Sample app doesn't seem to work

[damon-beaven]

https://developers.home.google.com/apis/android/sample-app/build

I've followed the instructions on the above link. The local Android project builds fine once I made the instructed changes. Everything links and it seems to pick up the downloaded Google Home library.

I've followed the instructions twice and I keep getting "User cancelled OAuth consent UI" from the app. I assumed the problem was in the Google Cloud OAuth project creation so I started over and created a completely new OAuth project but I get the same results. I also wondered if I had the wrong Android Studio signing key but I've followed the directions exactly as prescribed.

The flow that I see on my end is:

1. launch app
2. app says "permissions state: NOT GRANTED"
3. click "Google Home API Sample App" Button
4. Choose my google account (which has google home set up and is associated w/ the OAuth project)
5. I never see my Homes listed. I just get a flash on the screen and then the prompt saying ""Permissions Result: CANCELLED | User cancelled OAuth consent UI".

What else can I investigate from my end?

[YigitUyan]

Hi Damon,

Thanks for reaching out to us with the issue! As we described in the FAQ section of our developer site, the error you are seeing can be due to a range of issues (unmet conditions) on the permission flow (as we progress through the public beta program, our teams are working on making further improvements on logs produced by the SDK).

I would highly recommend to check the following:

• OAuth Setup: During the oauth registration on Google Cloud Platform (specifically, the oauth consent screen), make sure you allowlisted the test account you use over there and you are signing in with it.
• App Signing: Every app needs to be signed correctly, with the information registered as part of the OAuth setup. Whether you are using the default keys that comes with your Android Studio installation, or signing via the keys you created externally and sideloading the app as an apk, make sure that the information you provided (package name, SHA-1 fingerprint etc.) are correct.
• Customizing the App: If you are changing the package id of the app (which you provide as part of the oauth setup), make sure that you update it not only on the Android Manifest, but also on each individual file throughout the app.

We ask our users to create tickets in the Google Issue Tracker to follow up on debugging, which I see you have already done:
https://issuetracker.google.com/issues/390272619

Our teams will be in contact with you from there to provide additional debugging steps and tips,

Best,
- Yiğit

[damon-beaven]

@YigitUyan thanks for the reply and the feedback!

Yes, I have logged an issue. I've also double and triple-checked the points you have made. Everything is in order as far as I can tell. I'd also say that the Android Manifest no longer contains the package name in current Android development. I did update the package in all of the places in the sample though.

I'll keep an eye on the bug I logged to see what they discover.

thanks...

[damon-beaven]

I've located the issue. The instructions for finding the debug keystore are essentially incomplete. They don't tell you how to find the path and most users will use the default path b/c they don't know how to find the path any other way. Most online articles only point to the default keystore paths. In my case, there is a debug keystore at the default path but, for whatever reason, it is NOT the one that Android Studio is using.

This link provides the best way to get the debug keystore path through Gradle.
https://www.geeksforgeeks.org/where-is-debug-keystore-in-android-studio/