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.
Related
I'm stuck on configuring Apple Login for my web app using Firebase Auth.
I did all the configuration on https://firebase.google.com/docs/auth/web/apple but cant seem to find the apple-developer-domain-association.txt file to download and host on firebase hosting.
Firebase configuration:
Services Id:
- The bundle id on the identifier page
Apple Team Id:
- Full App name
Key Code:
- The key identifier
Secret Key
- Content of key file downloaded from the developers page
With this config I get the invalid_uri on the popup when opened.
Can anyone help?
Thanks in advance.
In addition to Ruaridh's answer, make sure that the "domain" is formatted with OUT the leading "https://"
so just: YOUR_FIREBASE_PROJECT_ID.firebaseapp.com
This may seem obvious to some, but I did not see anything in any documentation that specified the format the domain needed to be in. Even Firebase and Apple support were not able to identify improper formatting as an issue in my case. I came across this solution by accident and still cannot find any official documentation of formatting.
I had been stuck on that for a while, so even if it doesn't solve your issue, hopefully it is valuable to others.
You shouldn't need to host the apple-developer-domain-association.txt on Firebase anymore - I have just implemented Sign in with Apple on a Firebase web app and it wasn't required. Apparently as long as TLS 1.2 is supported (which Firebase handles for you), it should work. Firebase docs seem to be out of date. When configuring your Service ID, it says:
Your website must support TLS 1.2 or higher.
You should just need to register https://YOUR_FIREBASE_PROJECT_ID.firebaseapp.com/__/auth/handler in the "Return URLs" when configuring the Service ID in the Apple Developer Console.
Note that Apple doesn't let you use localhost as the return uri, so I found that I couldn't test it locally either.
I am developing an app to run on web and ios, using Expo (with rnw for the web component). I decided to begin to set up the app store presence today -- but I am running into issues:
We need your Apple ID/password to ensure the correct teamID and appID
Note: Expo does not keep your Apple ID or your Apple password.
? What's your Apple ID? MY_VALID_APPLE_ID
? Password? [hidden]
[16:22:23] Validating Credentials...
[16:22:24] Error while gathering & validating credentials
[16:22:24] Reason:Invalid credentials, raw:"Invalid username and password combination. Used 'MY_VALID_APPLE_ID' as the username."
[16:22:24] Set EXPO_DEBUG=true in your env to view the stack trace.
error Command failed with exit code 1.
I can log in just fine with these same credentials using the web. I thought to try to turn off 2FA, but apple doesn't allow that any longer.
It would be great if someone could verify that apple hasn't implemented a change for 2FA that broke expo -- I know expo started working with Apple's 2FA about a year ago.
I forgot to post an answer to this.
I can verify with certainty that it was not accepting my password containing a space, and that when I changed my appleID password, it began working. I submitted a issue with expo team and two people checked and said they had no such issue with a matching build environment. Apple never posted any outage details.
there was likely a small network problem that day where I lived that quickly resolved.
try running expo:build ios with powershell. It did the trick for me.
Does this link work?
https://appcenter.intuit.com/Playground/OAuth/IA
I am trying to get my QB online token secret required for working with a ruby gem. I have a valid QB account and I have entered my app's consumer key & secret. All I am trying to do is follow the instructions required to get the example app working from
https://github.com/minimul/qbo_api
Every time I click on the Connect to Quickbooks button, I just get an error message.
Oops! An error has occurred.
Please close this window and try again.
Error Code: no_access_to_this_field
Message: Team Intuit IA Application not allowed to get access to QuickBooks
I have changed the urls in my app and I still cannot get past the error message. I am at a loss since this seems to be a very basic step to start working with the gem. Please tell me the newbie mistake I am making.
Is there any other SDK I need to install? I do not have a Desktop version...just the online version.
So if anyone here happens to not figure out this answer already, its because I set the "Access Token Duration:" option on the Intuit Playground to 120 seconds...the default option.
I changed it to 1200 seconds by mistake, and the login works just fine now! I don't understand why that works, so if someone could answer that I could understand it better!
Thanks #William Lorfing
This can happen if you are using the playground to generate Oauth tokens for either QuickBooks or Payments access and you are not setting the correct data source.
See the answer here: https://intuitdeveloper.lc.intuit.com/questions/1247785
regards
Jarred
I am including sign in via google functionality in my app, for which i had created oauth client id keys for both of my debug and release mode, but since everything was not working properly so, i thought of deleting and re-creating it again, so i deleted both the keys but now when i trying to create the new keys it gives me error as
Duplicate fingerprint
The fingerprint you specified is already used by an Android OAuth2 client ID in this project or another project
but i had deleted both the key's, i had tried all the solution that are already present in stack overflow, like going into the old console portal etc. but none is helping me out,please help me with the issue
Did you try to go to your API console and UNDELETE your old projects? When you delete a project in the API console, the oauth IDs associated with it seems to not get deleted with it. I undeleted every single one and went through them and removed all associated APIs. Once I cleared out the past projects, I re-deleted them and added the oauth again to my new/safe project and it was OK.
Your problem seems to be little different, so you can look for different solutions here, as it's a common problem:
https://code.google.com/p/google-plus-platform/issues/detail?id=554
I am currently using the Salesforce.com IOS SDK Version 3.0 to build a native application that connects to salesforce. This app will be used for external users, so it is pointed at communities.
I first started by creating a Native IOS SDK app and getting that working and talking to salesforce.
I then created a new community, created a community user, gave them the proper permissions and finished setting up the community.
Next I went into the Xcode Project, under supporting files to the application plist. I then edited the SFDCOAuthLoginHost to be set to the community URL.
Once that was completed I restarted the app, and was able to login to the community through the native SDK and things would work great until the app hit its session timeout. At this point I receive these errors.
ERROR|SFNetworkOperation|callDelegateDidFailWithError Session expired or invalid
ERROR|SFNetworkOperation|Session timeout encountered. Requeue 0.000000or retry later
ERROR|SFNetworkEngine|Ignore session timeout error callback as host URL changed, request URL is https://dev-patientsupport-dev.cs21.force.com/dev/services/apexrest/patientNotifications, login host is [cs21.salesforce.com]
Of course because it cannot get a new session all web callouts fail after this point.
I have searched everywhere and cannot find a solution to this problem. My guess is that because the request is being made to the community URL, but the refreshed session is being sent from cs21.salesforce.com so it is being ignored. Thanks again for everyones time.
A fix for this bug has been submitted as part of Mobile SDK 3.1.1 patch on GitHub, npm (forceios), and Cocoapods. Please see https://plus.google.com/105428096535342044035/posts/AkoVwL5Kdt3 for more details.
It looks like this may be caused by the refresh token having its instanceURL set to the wrong destination when using communities. This may be a bug in the SDK as it works fine on the web. Try changing the instanceURL of the credentials to be the same as the URL of the community to see if that helps.