I made an iOS app (Swift) that signs in with Google, then fetches classroom data from the (Google Classroom API) https://developers.google.com/classroom. Everything was working correctly, and then some time later I think I accidentally deleted the Google Cloud project associated with it. So I had to re-create it and recreate an OAuth Client ID (I followed this guide on Google's website).
Now I'm getting an https status code 403 error - Permission Denied while trying to fetch classes, and I have no idea why. Does anyone know how to resolve this?
I believe the specific error (according to the Google Classroom API error section, linked above) is:
...but I'm very confused what to do to fix this.
One thing that is interesting is when I created an OAuth Client ID and downloaded the credential.plist (or credentials - can't remember) file and inserted it into the Xcode project, I get the same error as when the .plist file is not there. I'm wondering if I have it named something incorrectly? (Because before I had an entire GoogleService-Info.plist file since I had an associated Firebase project), but now that I don't need the firebase project anymore, I just have the credentials in the downloaded plist file which inherently is called credentials.plist.
Edit One strange thing is that I am only trying to read data, so I don't know why it's telling me I attempted to modify data.
If you are using some of the API to manage the classwork from the students with the Classroom API, you could be affected by this alert:
This could be interpreted in a way that, all the CourseWork that was managed by the previous Client ID is basically linked to that Client ID. This also has been discussed over the public issue tracker when it comes to Classwork created from the normal UI and how it can be managed:
https://issuetracker.google.com/issues/67748271#comment8
I would suggest to also share some feedback for this feature request so it gets the attention it needs. I notice that features like this for Classroom have been approved and implemented due to the high amount of users utilizing Classroom, generally it was previously limited however it has since been getting great support.
I have integrated Firebase Dynamics Links into my app (using <myapp>.page.link domain) and it's all working fine. However, I have now found that in my login and registration screens I get username/password autofill appearing for website page.link. I'm not currently using autofill, and don't have the webcredentials entitlement, so this is very strange. Has anyone else come across this and know how to prevent it?
I'm seeing it every time for each new project with dynamic links.
I think that firebase's apple-app-site-association posted at <yourapp>.page.link is the only credible source of info it can find (even though it doesn't have webcredentials). Basically it looks like after failing to find webcredentials anywhere it falls back to the only available file with applinks.
The easiest way to prevent this is to take initiative from firebase and post own apple-app-site-association file with webcredentials at your site (with proper "webcredentials:<your.domain>" counterpart added into the Associated Domains capability).
I've been working on my app with Firebase for several months now. I hooked up the password reset code about 5 months ago and when I would test it, I'd get the password rest email sent, click the link and everything would work fine. I haven't signed in with that particular account in 5 months so I forgot the password. Now when I get the pw reset email everytime I click the link I repeatedly get:
Try resetting your password again. Your request to reset your password
has expired or the link has already been used
I'm using Firebase 3 via cocoapods as of Aug 2016 and never upgraded or installed anything from any of the older versions. I'm also using swift 2.2, Xcode 7.3.1.
I would upload code but everything is working fine because the email is getting sent, the problem seems to be on FB's end.
What's the issue?
This is an update for anyone who runs into this problem. This is the response Firebase tech support sent back. It isn't the answer but rather an idea of what they'll ask you if you have the same problem. You get up to 5 free questions per 365 days so why waste one.
Hi there,
Could you please try resetting your password on your console and let
us see if it works there. Also, did you generate a new API key for
your project? If yes, then it's possible that your old API key is
still being used by your app. Could you please check whether the API
key is same? The API key from your Firebase project and your app
should be the same.
Please update your app's Firebase config and check if the API keys
match your console's. For Android, download the updated
google-services.json file. See more details here. For iOS, download
the updated GoogleService-Info.plist file. See more details here. For
Web, follow the config as seen in the docs. If the steps above still
doesn't work, please provide the details below to further investigate
the issue. Old API key and new API key used. Platform and Firebase SDK
version used? Date and time you started encountering this issue. Error
logs and full stack trace. Screenshots of your API keys. Let me know
if you have any other Firebase related issues/questions. Thank you for
using Firebase. :)
I actually had another API key inside my console that was never used. I deleted it like they suggested and the Firebase Recovery email was still broken. I changed my Google.Console password and it still didn't work. I sent them all the required information. As soon as I get a response and hopefully a resolution I'll post it.
I had the same problem. I couldn't understand why and then I realised something... as it was new environment, I exported users from another environment and on this one, I just forgot to activate authentication by email...
My mistake but I thing Firebase should make it clearer in their error warnings.
When I am signing into Gmail in my iOS App, I am getting the below error (screenshot) and the sign-in fields do not appear. We are loading the sign-in screen in a WKWebView.
We are using a custom URI redirect but why is google throwing this error now. What are the alternatives to a custom URI?
Swift 2.3 project
Using OAuthSwift v0.6.0 cocoapod
This started quite recently only in the past week or so I believe something changed with Google's APIs.
I have read that google is deprecating webviews for OAuth and will block requests on April 20, 2017. As seen here in a Google Developers Blog:
https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html
Does this mean I already need to use or is there another viable solution? I thought I had more time before needing to update this.
My guess is that your client is registered incorrectly in Google Cloud Console. A 'WEB' client is typically a server or Javascript application. An iOS app should be registered as an iOS client.
https://developers.google.com/identity/protocols/OAuth2InstalledApp#creatingcred
I Just found this problem too.
Please check google developer console and look at the credentials keys
Your Client ID in google-info plist must come from iOS application, not the web.
And use that Client ID to be revereseClientID and copy it in to URI type
I have solved the problems by create project in Fire Base Because REVERSED_CLIENT_ID generate from developers.google.com Incorrect.
Try create your project in FireBase
https://console.firebase.google.com
you must cross check clientId at your 'Google Dashboard' clientId and clientId at "GoogleProject.Plsit".if both are different, copy ClientID from 'Google Dashboard' and paste it on "GoogleService-Info.Plsit".and also amend your reverseClientId in "GoogleService-Info.Plsit" according to newly pasted ClientID(you check the pattern how reverseClientId created from client Id in "GoogleService-Info.Plsit"). And then paste thid reverseClientId in 'URL type' in your project setting.
In case of mine clientId on "GoogleService-Info.Plsit" and my 'Google Dashboard' were different.
chech your google dashboard here : https://console.developers.google.com/apis/credentials?project=firebase
I just experienced this issue following the Google Signin for iOS Guide. The plist generated file is not the good one. You need to take a look at the clientID and reversedClientID and be sure that they are the ones for the iOS app on your Google developer portal.
I faced this error after previously creating a GoogleService-Info.plist file using the site Google Sign In directs you to. I later started using Firebase, which seems to create a separate .plist file. After attempting to include Firebase's new .plist file, my Google Sign In button started yielding the invalid_request error with the Custom scheme URIs are not allowed for WEB client type message.
In order to fix the problem I tried many things, but in the end deleting MY ENTIRE Firebase project on their web console (not just the individual app), recreating a new Firebase project from scratch, and re-downloading the new .plist file, solved the error.
It creates two client ID. one for web and one for iOS application. Web client will be in the google plist by default. So it gives the above error. Use iOS Client id from google console or create credential for iOS application.
For my experience, I had followed Google's SignIn iOS Swift guide and had downloaded a Web OAuth JSON file. They literally provide you the wrong Plist file for an iOS setup.
Just in case somebody else runs into this issue here are the steps I followed:
Go to the Google Developers console.
Go to the Credentials section.
Notice there are two items in the "OAuth 2.0 client IDs" section. (If you previously attempted to configure an iOS Google SignIn project.
Click on the name of the "iOS client for ".
Click "Download PLIST File".
Delete the Google web Plist file from your project.
Drop in the new iOS based Plist file.
Copy over the new REVERSED_CLIENT_ID into your URL Types of the Info page of your project. (This is detailed in Google's guide).
Attempt to run your app again.
Note: I got the Google Sign In API to work with Swift v3 and XCode v8.
I was getting the same error. Then I figured out, that I did not provide my app Bundle Id to access the Google Sign In Service in my app.
You do that from the page with the link:
https://developers.google.com/mobile/add?platform=ios&cntapi=signin&cnturl=https:%2F%2Fdevelopers.google.com%2Fidentity%2Fsign-in%2Fios%2Fsign-in%3Fconfigured%3Dtrue&cntlbl=Continue%20Adding%20Sign-In
1.Sign in with your Google Developer account.
2.Create you app name and copy the App bundle Id from your project from:
Project and Target List> General> Bundle Identifier.
3.Choose your Country
4.Enable Google- Sign In.
Then perform the necessary steps to integrate Google Sign In in with your iOS App.
I was facing the same issue. I followed all the instructions to integrate my app several times, and played with the code to see if there was any hidden issue in the code.
I downloaded and configured the sample app from google at github https://github.com/googlesamples/google-services and go the same issue, so it was not the code.
It seemed like there is something in my console configuration so I switched between different google console apps, and played changing the bundle IDs.
The only thing that managed to fix this issue was to use Firebase instead. I created an app in the firebase console, downloaded the new plist, and it worked.
Still not sure why this didn't work for me in the first place, this doesn't seem to be a common problem, but I hope this helps someone.
cheers,
Kindly check console.developers.google.com/apis/credentials for your project and see whether there is already a client_id in OAuth 2.0 client IDs section , if so then copy that client id and replace it with you GoogleService-Info.plist file's CLIENT_ID and accordingly change REVERSED_CLIENT_ID (in reverse manner) now clean and build your app and test it will work
I was using Meteor with Cordova and Meteor's official google integration, which relies on cordova-plugin-googleplus.
I had to:
create both an iOS and a web Client ID
use the web Client ID on the settings / server / database as documented
but then use the reverse of the iOS web client as the REVERSED_CLIENT_ID for cordova-plugin-googleplus
Expo, authentication with Google.logInAsync from expo-google-app-auth
In my case I just used androidClientId instead of androidStandaloneAppClientId
I want to sign a BlackBerry application with the 3 CSI files I have. When I install new keys, I give the associated user id and password, but I am getting this error:
Unable to register a client bearing no
175534 because there are no more
registration attempts. If you have
already registered with this server
then you must contact RIM to register
additional users.
Can anybody tell what is next step that I need to do?
The error message seems pretty clear on the next step:
.. you must contact RIM to register additional users.
The official response from blackberry support:
Hello,
Thank you for contacting BlackBerry Application Development Support.
This error means the keys have already been registered so cannot be registered again. To have this issue resolved a new set of signature keys will need to be issued and installed. Please note that signature keys are now completely free and issued several times a day, so the fastest way to get a new set would be to place a new order:
https://www.BlackBerry.com/SignedKeys
Prior to installing this new set of keys please first delete all present CSI files as well as the sigtool.* (DB, CSK, SET) files that will reside in the sub-directories of all development tools. Make sure to write down the PIN used to place the order as well, it will be needed when installing the keys.
After registering your keys and verifying that they are able to sign I would recommend backing them up some place safe in case anything should happen to your development environment:
http://supportforums.blackberry.com/t5/Testing-and-Deployment/Backup-and-Restore-BlackBerry-Code-Signing-Keys/ta-p/837925
Go to the first URL and request a new set of keys. You should get an order confirmation email right away. In about 1-2 hours you will get 3 more emails. Each one will have a CSI key attached. (The keys are free to generate)
To avoid this issue in the future, you can back up the keys, according to the instructions in the second link (above).
Good luck!