DarkKor / google-api-objectivec-client

Automatically exported from code.google.com/p/google-api-objectivec-client
0 stars 0 forks source link

"Error: redirect_uri_mismatch" upon attempting login to Google Calendar account through sample #22

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
   1. Install and build the Google Calendar sample.
   2. Run the application. Create a client ID and client secret, and enter them into the Client ID and Client Secret boxes.
   3. Select Login and enter the username and password of a valid Googel Calendar account.

What is the expected output? What do you see instead?
   Expected output: Successful login.
   Actual output: "Error: redirect_uri_mismatch - The redirect URI in the request: urn:ietf:wg:oauth:2.0:oob did not match a registered redirect URI."

What version of the product are you using? On what operating system?
   The latest Google Calendar API svn, build with Xcode 4.5.2 under Mac OS 10.8.2.

Please provide any additional information below.
   Looks like a URL hardcoded into the sample API is incorrect or is being mishandled.

Original issue reported on code.google.com by sfs...@gmail.com on 18 Jan 2013 at 10:04

GoogleCodeExporter commented 9 years ago
And here's the "Request Details" section:

Request Details
   from_login=1
   scope=https://www.googleapis.com/auth/calendar https://www.googleapis.com/auth/userinfo.email
   response_type=code
   access_type=online
   redirect_uri=urn:ietf:wg:oauth:2.0:oob
   as=4ea98e6be6c291a9
   display=page
   client_id=320741315329.apps.googleusercontent.com
   hl=en-US

Original comment by sfs...@gmail.com on 18 Jan 2013 at 10:17

GoogleCodeExporter commented 9 years ago
Be certain that you are using a client ID and secret created for an installed 
app type "other" (not type iOS)

http://code.google.com/p/gtm-oauth2/wiki/Introduction#Registering_Your_Applicati
on

Original comment by grobb...@google.com on 18 Jan 2013 at 10:31

GoogleCodeExporter commented 9 years ago
Not really a library issue.

Original comment by grobb...@google.com on 22 Jan 2013 at 10:46