Parse invalid session token error 1.8.2 - ios

I am currently getting this error in the terminal of my application when I run it. It was working fine not to long ago but now I am getting an Invalid Session Token error and I'm not sure why. I have tried to resolve this issue with no success.
I have tried reading upon this parse help tutorial on how to fix this error with the link https://www.parse.com/tutorials/session-migration-tutorial, but when I try entering that line of iOS code in the line below where I enter the client & Application ID, it does not run (I get a failed error).
I have also have "Require Revocable Sessions" enabled in the dashboard of ma application which it says to do in the link provided.
If anybody else is having this issue and can help me solve it, that would be fantastic, thank you!

This is clearly stated on the dashboard and in the documentation. If you enable "Require Revocable Sessions", all sessions that use legacy tokens (non revocable) will be invalidated and you will have to login again.
You have 2 possibilities :
Your app is in production and you have users using it with an old version of the SDK (meaning they use old tokens). Then you should disable "Require Revocable Sessions" immediately.
You're still developing your app, then leave "Require Revocable Sessions" enabled, do not add the migration code and just re install your app.

Related

LinkedIn SSO: the authorization server encountered an unexpected condition

Since 2AM (ish) this morning, the SSO does no longer work with LinkedIn.
We 100% get the error "the authorization server encountered an unexpected condition".
We did not change our code whatsoever. We tried to switch the LinkedIn developer app to test mode and then back to live mode, but still no luck.
There can be no logs on our end (for the issue is on LinkedIn end), and AFAIK there is no developer log on LinkedIn either (although it could be a pretty useful addition).
Anyone experiencing the same issue? Or anyone have any idea why this could happen all of a sudden?
Thanks!
EDIT: after several attempts (by modifying our OAUTH code in some ways), it always failed. And we decided to create another brand new LinkedIn developer app, and it did work! This is really weird...

Firebase 3 Password Recovery Link Not Working

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.

Unable to be connected to Quickbooks through Intuit App Centre | Playground

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

deugging login error canvas app - rails - facebooker

I have inherited an app set up using built using rails using the facebooker gem. It's hosted on heroku.
I'm getting reports of users getting the following error when they try and grant permissions -
An error occurred with . Please try again later.
I've had a look through heroku's logs and can't see any errors.
Any advice on how I should debug this?
I'm going to answer my own question. I presume no one else will due to the abysmal lack of information that I provided.
the reason I'd not encountered this error before was because Facebook forced a relocation of apps to secure servers recently.
I'd neglected to change my app url in my login javascript to 'https'
Firefox & chrome did not notice the difference. Internet explorer 7 did.
In a nutshell - make sure you have the correct domain name in your facebook app settings.

Atempt to access security API

My project was working fine couple of minutes ago,all of a sudden i run the code and i get
the error below,i added a class but then deleted it,this is how i got the error and i cant seem to grt rid of it,ive cleaned the simulator and my project and when i debug this is the error i get
Module 'StreamingPlayer-1' attempts to access a secure API.
[0.0] AM: Error starting StreamingPlayer: Module 'StreamingPlayer-1' attempts to access a secure API.
....please how do i fix this,
thanks
You have to sign your application! read this...
Code Signing Keys
module attempts to access a secure API
You get 3 CSI Files from RIM when you ask for signing keys. You have to install all three of them before you can effectively sign your app.

Resources