Got origin_mismatch error in Google+ share api

2019-01-14 11:12发布

I want to share some dynamic content on google+. For this I checked it https://developers.google.com/+/web/share/interactive#rendering_the_button_with_javascript

<head>
<script type="text/javascript">
  (function() {
   var po = document.createElement('script'); po.type = 'text/javascript'; po.async = true;
   po.src = 'https://apis.google.com/js/client:plusone.js';
   var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s);
 })();
</script>
</head>
<body>
<button
  class="g-interactivepost"
  data-contenturl="http://www.pubandbar-network.co.uk/" 
  data-clientid="102180630313.apps.googleusercontent.com"
  data-cookiepolicy="single_host_origin">  Share 
</button>
</body>

But when executing I am getting this error

Error: origin_mismatch
Request Details

    scope=https://www.googleapis.com/auth/plus.login
    response_type=code token id_token gsession
    access_type=online
    redirect_uri=postmessage
    cookie_policy=single_host_origin
    proxy=oauth2relay554026710
    origin=http://www.pubandbar-network.co.uk
    state=1995523240|0.4607792083184853
    display=page
    client_id=102180630313.apps.googleusercontent.com
    authuser=0

Please suggest how to fix this

16条回答
疯言疯语
2楼-- · 2019-01-14 11:41

The most common oversight resulting in this error is forgetting to add both HTTP and HTTPS origins on the consent settings in the App Credentials dashboard.

To fix, go to https://console.cloud.google.com/apis/credentials?project=YOUR-APP-ID

Select the OAuth 2.0 client IDs if you had already created one.If not, you will have to create a new client ID for your origin.

Under Authorised JavaScript origins, add both https and http origins for you app if had not added both.

查看更多
Viruses.
3楼-- · 2019-01-14 11:44

Origin mismatch is normally caused by the Javascript origins not being set correctly in the API project console. You need to make sure that the Javascript origins match the domain from which your requests are coming and to which you are returning the user after sign in.

More details can be found in the developer documentation in the "Create a client ID and client secret" section.

Note: A common mistake here is to add javascript origins for http:// but not https:// (or vice versa). If you want to allow users to access your site from both then you need to list both in the javascript console.

Note (Thanks Bethel Goka): You must include the port number of your server in the javascript origins if a port number appears in the url when users access your site.

查看更多
Luminary・发光体
4楼-- · 2019-01-14 11:44

If your client id, client secret, and your javascript origins url is correct you might want to check whether the port you're using is exactly the same with the url you put in for javascript origins. I mistyped mine by one digit: e, g localhost:888 instead of localhost:8888 and got that error because my javascript origins was localhost:8888 not 888

查看更多
聊天终结者
5楼-- · 2019-01-14 11:45

I had this error trying to use the "Google Play Games Services Management Demo" and it was because of missing "www" in the URL

查看更多
Summer. ? 凉城
6楼-- · 2019-01-14 11:47

1: Open the Credentials page for your project.

2:Double-click on your OAuth 2.0 Web client in the client ID list.

3: Make sure that in the web client ID form, change the Authorized JavaScript origins field to http://localhost:8080 when you are running the server locally. When running remotely add the corresponding appspot server url.

查看更多
老娘就宠你
7楼-- · 2019-01-14 11:47

You must read the developer guide here

https://developers.google.com/analytics/devguides/reporting/embed/v1/devguide

Good luck !

查看更多
登录 后发表回答