Whenever I try to login to my AppStore connect console, I'm getting redirected to this page(https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/gettingstarted). This looks like to be older iTunes connect page which is no longer operational. I'm not able to access my AppStore connect console at all and have been facing this issue from past 5 to 6 days. Have also tried accessing it from other browsers and in incognito, nothing seems to work. Any idea what would be the reason? Anyone else facing this issue?
I contacted the Apple Support for this issue, but they couldn't figure out the issue right away and asked for some time to investigate the issue.
Meanwhile I could get credentials of our accounts team-agent and on logging in with his credentials we saw that in the Users and Roles section all the users were removed except the team-agent, even the admins(which was my role). And this was the reason why I couldn't access the App Store Console. The team agent user also confirmed that he has not deleted any of the users.
So, post realising what was the issue, we just added all the team members again in Users and Roles section, post that it's working fine. We also informed the apple support regarding what had happened, but they were not able to figure out why the issue occurred and told us to inform them if it ever reproduces again in future.
Hope this helps! :]
Related
I am trying to migrate from Fabric to Firebase Crashlytics but it is not going through. I am already logged in and the system still asks me to login. Moreover the sign in with Google to get started button does not respond. When I click on the small button beside profile, it redirects me to the Fabric dashboard but I still see no option whatsoever to connect both the accounts. Can you Please help me here?
It seems that using safari has helped but also, using incognito mode should work.
Incognito mode should work. It force user to enter the credentials (i.e user name and passwords) and if issue still persist check, if you have an aggressive adds blocker plugins or inspect the developer mode for any 400 and reach our "support#fabric.io"
Since few days I have problems with the API instagram. Instagram sending this error page after the user has entered this login information.
"This page could not be loaded. If you have cookies disabled in your browser, or you are browsing in private mode"
Do you know why ? How to do ? Need help
On webapp authentication... the problem is related to instagram platform. I found that the problem arise only if your browser don't have the instagram cookie "ig_cb" set. This is set when you accept cookie policy on instagram.com. The workaround is to go on instagram and accept cookie policy then go back to your social auth and proceed.
This happens for both mobile and desktop users (browser).
Being a block on instagram login process... I guess there's no definitive solution other than wait for instagram bug fix.
I hate to be the bearer of bad news, but we also had this problem, which flagged on the Facebook Dev page: https://developers.facebook.com/support/bugs/406930029718049/
They have looked into the problem, as a number of us have had this exact issue too. It is only affecting EU user, as our US users are logging in and signing up without problems, and it seems that Facebook are refusing to look into it - their Instagram Platform API forum has already stopped accepting issues.
In terms of what we have learnt since last week, we think:
It is likely GDPR related
Not all apps have been affected, Bumble does not have this problem but Tinder does
It is happening with both the old Platform API and Graph API, according to a developer who has already migrated to Graph.
No one seems to know anything!
UPDATE:
So it seem's it is in fact a cookie issue on mobile. When a user goes to sign in on mobile view, the 'accept cookie' message that typically appears on web doesn't appear. However, when the error screen pops up, if you click 'Log in' in the top right, it will redirect you to the web view, which lets you accept the new terms and conditions. Then, once you direct back to mobile the cookie seems to have been saved and you can now login. This has worked for us on iOS so far, but not Android, and we still haven't come up with a work-around yet.
This bug has now been fixed.
Thank you all for your comments, individual input, and patience while we worked to address this issue for everyone.
I am happy to report that this particular issue with Instagram login should now be resolved, but if you are still seeing any issues related to this fix, please let us know on this report only.
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...
There was a erfectly functional 1.6.1.7 prestasite before trying to upgrade, we since tried to restore but not all files copied over as per Softaculous.
The issue is users are unable to create an account nor existing users able to log out. Error debug is one and does not show anything. bedandwood.com is the site. I ensure header.tpl has a centre column but most of the code is untouched. Is there something in cookie or token that is causing the issue?
Thank you
We reinstalled the shop, given there was no response.
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.