Skip to content

Instantly share code, notes, and snippets.

@im-coder-lg
Last active November 27, 2023 14:57
Show Gist options
  • Save im-coder-lg/23fc93cbf983b36b21641563ed4f3d4e to your computer and use it in GitHub Desktop.
Save im-coder-lg/23fc93cbf983b36b21641563ed4f3d4e to your computer and use it in GitHub Desktop.
Allows GAUDC permission to personal results if you do this.

About this gist

So, today, I found a person(change-agent) telling about the fact that GAUDC does allow personal requests. But it was complicated so I made a guide.

Actually, the Google Assistant SDK used by GAUDC was changed to remove personal results but by reengineering it, people in the GAUDC community figured out how to allow personal results.

This is the advanced guide and if you want the real one, hit this and if you want the original, click here. Thanks to morgenman and change-agent for that reply that helped me to make this!

Steps:

  1. Go to the Actions Console.
  2. Go to your GAUDC project
  3. Go to the Develop Section.
  4. Hit the hamburger button on the left side of the Develop screen and go to Account Linking.
  5. Now, enable Account linking by switching the toggle.
  6. Choose yes for Account Creation.
  7. Hit Google Sign-in as the Linking Type.
  8. After that, get your phone ☎️ as you will need it.
  9. Open GAUDC and ask your name.
  10. Take your phone, open the notification center, and click the Google request notification.
  11. Give some or the other name, eg. Google Assistant from my PC.
  12. Allow the Personal Requests request.
  13. Ask GAUDC your name, not your phone Google Assistant/Siri(in case you use an iPhone).
  14. It will successfully respond.

Voila! Hope this helps everyone! Look at this:

Steve Jobs! Nickname lmao i am funny sometimes

See you later!

@im-coder-lg
Copy link
Author

oops 671 sorry for that!

@Rocked03
Copy link

Rocked03 commented Apr 1, 2022

No worries, thanks -- I've seemed to manage to have gotten a new token, but I'm still getting the same "error getting tokens" error. This isn't really that urgent for me though, and since there seems to be a bunch of people with this problem, I'll probably just wait until it gets fixed. Thanks for the help though!

@aaron-gray
Copy link

Despite the fact that I've enabled personal responses in the app on my phone and given the device a name, GAUDC still keeps prompting me to enable personal results and sending more notifications to my phone. Account linking is enabled i the action console, but doesn't seem to make a difference. Even tried deleting everything and starting from scratch--no luck.

@im-coder-lg
Copy link
Author

Hmm... Well, the loophole could have been fixed, idk how

@LaLino1
Copy link

LaLino1 commented Jun 3, 2022

I had the same error, but I "recently" solved it, I realized that I was using the web client to be able to use the GAUDC (I've been using it for a long time because of the error that there is) but since I wanted to have the option of reminders (testing some things), download from the Google Cloud Platform in the Credentials option "OAuth 2.0 client IDs" the desktop type .json file. Change my "web client" file, replace it with this one with a new token and that's it.
Since I don't have a cell phone, I used an emulator, I asked the question about my name, (as I had done before and nothing happened) I activated the "personal results" option, I did nothing else I gave the arrow to return , I enter the GAUDC I ask the question and notifications no longer arrive and it works without problems.
I have to say that I created a "new project" thinking that something was wrong when creating the previous one, but even so I had the same error, then I did this and I no longer have it.
Espero aportar en algo ;3

@im-coder-lg
Copy link
Author

im-coder-lg commented Nov 27, 2023

There has been an update on this(finally!). GAUDC Issue 863, with issue comment ID - 1474980944. Requesting everyone who actually sees this(lol) to refer to that and try this, while I update the gist, and maybe post it on my Astrosite blog for easy sharing(:shrug: we shall see)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment