Good afternoon! I want to confirm the integromat app in the Google app to upload my own files to Google Drive. Moved to the moderation stage, but the message "Comply with domain verification requirements"appears. Tell me, how did you solve the problem of checking the application in the google cloud app and the integrator service in order not to reauthorize the application every 7 days?
Assume that you already verified your domain and still getting this error, try to do this:
Go to your "Google Console" > "OAuth Consent Screen" and under "Publishing status" click "Back to testing"
Now you are back in the test mode, click "publish" again
You may see some new demands to publish it, which were unknown before. You could follow these demands now.
After that, you will see "The Trust and Safety team has received your form." message.
Related
New Matillion user, and my first project is to read in Google Analytics data by using a google account authorized to access GA data from several clients.
I follow the steps from this Matillion documentation: Google Query Authentication Guide
I have setup the needed client ID and client secret, and I've pasted the redirect URL into the credentials page in the Google console.
From Matillion, I enter the client ID and secret in the OAuth Configuration dialog, and I configure the proxyserver and proxyport under "advanced connection options" as specified in the Matillion documentation.
When I click the Authorization link in the OAuth it opens a new tab to the Google page where I login and allow the access. Once I do this, the redirect seems(?) to kick in and I presented with a browser page with the message "Authorisation complete Please close this tab". I am not taken back to the tab where Matillion OAuth configuration is still waiting for a response of some type.
Any ideas with this? Additional information: I setup Matillion via the Snowflake Partner Connect console and am still in the free 14-day trial for Matillion.
I was able to get the OAuth workflow to finish. Any issues from this point forward will be a battle for another day. Here are my findings:
First note that I initiated my Matillion install from the Snowflake Partner Connect, which was very straight forward. I was up and running with Matillion in less than a minute.
The Matillion version that launched was 1.50.6, which is behind the most current version 1.58.4. I had no idea this would not be the most current version, as I assume the cloud platform might provide new installs with the latest version. I can see reasons why this might not be the case.
After several hours ensuring my GCP project, client id, client key, and other settings were correct everywhere, the workflow still would not complete. I opened a support case with Matillion and it was responded to within 2 hours. That is excellent. The first recommendation was to update Matillion to the latest version as it will address an OAuth issue resembling the one I reported. I saw the new version was very recent, and didn't realize I was nowhere near having the latest version.
After the update completed, I tried repeating all of the same steps. The only difference now was that the "Authorisation complete" tab closed on its own returning me to the Matillion tab which still sat "Waiting for response from service...". The version update seemed to show promise but not a solution.
A comment Schepo above cleared the final hurdle: I removed the proxyserver and proxyport "Advanced Connection options" from the OAuth configuration, and then tried getting a new authorization link. Matillion froze up and the session was dead. I had to close the browser, open a new incognito window and repeat the steps - without the proxyserver/proxyport connection settings. This time the workflow completed!
The Matillion documentation for Google Query: https://documentation.matillion.com/docs/2339840 should be updated if the Proxy Settings are not required for all OAuth configurations. The OAuth issue I reported should also be documented somewhere as a known issue addressable by the latest version (if not already).
OAuth being one of the many ways you can set up connectivity with Snowflake; it appears you're attempting to set up External OAuth, that is Google is the authorizing server. My understanding is that there are two paths to setting up OAuth,
This link has the Azure AD setup with the two options, https://community.snowflake.com/s/article/Create-External-OAuth-Token-Using-Azure-AD-For-The-OAuth-Client-Itself
Googling to setup Google AD returns https://support.google.com/cloud/answer/6158849?hl=en
You may have to follow a similar process, follow this content here: https://docs.snowflake.com/en/user-guide/oauth-ext-custom.html
I have configured google assistant in my raspberry pi as mentioned in the below link
https://developers.google.com/assistant/sdk/guides/service/python/embed/run-sample
In the google action console, i have given permission to all the activities.
But when I tried assessing google calendar through google assistant in my raspberry pi, Google assistant module doesn’t show my calendar anymore.
It says " First I’ll need your permission to give Personals Results. You can make that change in Google Assistant Settings on your phone."
Then I receive a notification on my phone to allow permission
As soon as I click on “Personal results” to allow permission on phone, the app crashes. I have tried 2 different phones but same thing happens.
So I deleted token & credential file and used a new credentials (auth), allowed all permission but it still gives me the same message when I ask for my personal results such as calendar.
Has something changed? Could someone help to solve this issue?
The custom domain wizard in firebase cannot go in the "verify ownership" stage. When I look at the web dev console I see a lot of 503 errors.
Is the spark plan not enough to have a custom domain ? Is the system broken ? Have I skip a step ?
For anyone else who ends up here, I did forward this on to Firebase Support.
They responded with 'That error appears when developers have a GSuite account. To solve the issue, reach out to your GSuite organization admin/owner to get the Search Console enabled. The following Google support article will provide the steps to enable the Search Console.'
Indeed, after enabling the Google Search Console, it did proceed to the Verify Domain step.
I am creating a project to be able to share a Calendar among some users.
The strange thing is that when one of the users wants to connect, the following error appears telling him "This app isn't verified"
https://prnt.sc/p87wvm
I am not a programmer so it is difficult for me but I think I am doing everything right.
The only api that I am using is that of Google Calendar.
The email with which I am creating the Api is a #gmail.com
https://prnt.sc/p88o0g
I am not using any special scope that requires some type of verification.
I did not exceed any quota limit or anything like that.
And the send to verification button is disabled and tells me that my changes do not require verification
I want any user with a Gmail email to connect to the calendar
What i need to do??
For the doubts I have verified the domain thinking that it was that but it did not solve the problem either
5I'm creating a google actions for Google Home, i'm using dialogflow and firebase functions and database to create the all thing.
So far everything was working good together but yesterday an error occured that i dont understand.
When i want to test my agent on the Simulator section of Google Actions, the agent is not responding even if in the logs i can see that the response is actually received by the simulator as shown here
And it answer this in the simulator
The response is empty and i have this simple error in the Debug section
It worked perfectly before but i may have change one thing that crashed everything and i can't find it.
EDIT
As recommended by #Prisoner, i've checked the History to find this
So i checked the logs and i got this (after Dialogflow Request and Dialogflow fulfillment request who were looking good)
It seems that the Dialogflow fulfillement response is having problem with URL ???
EDIT2
My URL fulfillment (firebase functions) was wrong, now that i have changed it, the log in my History seems ok :
But i'm always getting the same error on the Simulator.
Your logs show that your fulfillment is not deployed correctly and the URL is pointing to a HTML 404 page. This will cause your app to stop responding.
You may be running into the recent "first TTS is not spoken" bug in the simulator. I suggest changing your surface to speaker instead of phone. You can read more about this here.