cancel
Showing results for 
Search instead for 
Did you mean: 

Privacy_policy_url cannot be empty – field not found in Google Home Console

GuillaumeK
Community Member

I try to create a cloud to cloud integration but :

Error creating account linking for project(xxxxxxxxx) due to 
(INVALID_ARGUMENT: com.google.identity.accountlinking.error.AccountLinkingException:
<eye3 title='INVALID_ARGUMENT'/> generic::INVALID_ARGUMENT: privacy_policy_url cannot
be empty [type.googleapis.com/util.MessageSetPayload='[google.rpc.error_details_ext] { 
message: "privacy_policy_url cannot be empty" }']).Please try saving again.

No field to create a  privacy_policy_url URL on the form.

1 Recommended Answer

arm_dpe
Solutions Expert
Solutions Expert

Thanks for sharing this. The issue has been addressed, and the fix will be rolled out over the next few days. Please try again in the next few days and let us know if the problem persists.

View Recommended Answer in original post

7 REPLIES 7

Godiak
Community Member

I can reproduce the “privacy_policy_url cannot be empty” error in a brand-new Google Home Cloud-to-Cloud project.

 

Already verified:

- Branding saved in Google Auth Platform

- Homepage / Privacy Policy / Terms configured

- Authorized domain configured

- Company profile submitted

- Privacy policy URL is publicly accessible

 

The error still appears when saving Cloud-to-Cloud setup, even in incognito and from another device.

 

This looks like a console/backend issue rather than a missing field in the current

Is this a known issue? Is there any workaround?

berezhnyi
Community Member

The same issue for me for creation and update cloud-to-cloud intefration

Anjalo133
Community Member

Bbhhbbkkcddtu45778hg

iotcri
Community Member

Same issue is happening for us too.

arm_dpe
Solutions Expert
Solutions Expert

Thanks for sharing this. The issue has been addressed, and the fix will be rolled out over the next few days. Please try again in the next few days and let us know if the problem persists.

rsherga
Community Member

Thanks for the update. Please note that the latest update to Issue 503782518 from Google's side references "Friday May 25th" as the anticipated fix date. Can you please provide a correction in the ticket to whatever it is supposed to actually be?

There is no 25th on a Friday until September, but April has a 24th on a Friday so I assume that's what was intended...

 

Thank you