I recently came across an issue with Facebook Login after updating to iOS 13 and Xcode11. Login worked fine, all doc configuration is correct but two of my apps have this error now.
-canOpenURL: failed for URL: "fbauth2:/" - error: "This app is not allowed to query for scheme fbauth2
There is a similar question but it relates to iOS 10, and the issue clearly states that the info.plist configuration was incorrect, which is not the case here.
-canOpenURL: failed for URL: "fbauth2:/" - error: "This app is not allowed to query for scheme fbauth2" (OSStatus error -10814.)
Upgrading to the current FBSDK should resolve the problem. iOS 13 requires the implementation of ASWebAuthenticationPresentationContextProviding, which was not available until FBSDKCoreKit 5.4.
FBSDKCoreKit/FBSDKCoreKit/Internal/BridgeAPI/FBSDKBridgeAPI.m was modified to support iOS 13's requirement to implement ASWebAuthenticationPresentationContextProviding in FBSDKCoreKit 5.4. (The current version is 5.8.) Versions prior will no longer work.
The needed change is posted here: https://github.com/facebook/facebook-ios-sdk/commit/6b061099f339ef0e8bde2e2c2163ef5a3c1b8340#diff-72593591275d63edfb1bfad837e4c32f
I was unable to upgrade due to a dependency with AWS, but I was able to patch the 4.42 version of the file based on the differences in the diff above.
The error -canOpenURL: failed for URL: "fbauth2:/" - error: "This app is not allowed to query for scheme fbauth2 was a symptom of the FBSDK attempting to open Facebook, which was not installed, so it was just a warning before it would fall back to browser-based FB auth.
Related
I'm getting the following error on the Ohio server:
Failed to authenticate user due to missing information in request.
This suddenly started happening after using Glue for few months.
Error picture here
I've tried adding AWS onto my cookie allow list and still doesn't allow me. I've also tried restarting my machine and using another 2 browsers other than chrome yet still doesn't work. I'm the only one affected on the team it only happens on the Ohio server whilst NV etc work perfectly.
I had the exact same issue. Check that your browser does not block third-party cookies. Any browser that blocks third-party cookies either by default or as a user-enabled setting will prevent notebooks from launching (the typical error message is Failed to authenticate user due to missing information in the request.)
Chrome: Turn Off "Block Third-Party Cookies" in Chrome for Windows
Firefox: Third-party cookies and Firefox tracking protection
Safari: Clear cookies in Safari on Mac
I've followed closely this tutorial which is great.
Everything worked fine until today, where when I log with github I get this error:
HTTPError at /oauth/complete/github/
403 Client Error: Forbidden for url: https://github.com/login/oauth/access_token
What am I missing / what could I have changed?
I'm currently developping a Website with social networks login.
Everything works fine (google, facebook and twitter) but not github: after some attempts, I'm getting now a 403.
The problem in Django is that 403 errors dont show the HTML content that come with the error!
I had to run in Debug mode and add a breakpoint in the file
/usr/local/lib/python3.7/site-packages/requests/models.py
line 940 / where there's the code raise HTTPError(http_error_msg, response=self)
Inspecting the variable self.content.decode("utf-8") showed me that I've been restricted (for no logical reason - what's more strange is that the same code, on my same PC but under Windows, works like a charm).
I'm hoping the technical team at github will explain what went wrong...
How do I get a registration code or otherwise solve this problem?
While writing this question, I realized the crux of this problem is the bottom-most part of this question: I'm not getting the popup I'm supposed to get and when I enter the URL in a browser it says invalid registration code.
I'm attempting to develop an Alexa Voice Service application. Website/companion service only. I have gone through the Reference Implementation Guide twice and have double checked that all of the setup has been done correctly.
This is the server error I get: invalid registration code. I never did anything with a registration code and can't seem to find anything about a registration code (relevant to Alexa) anywhere after googling quite a bit.
Listening on port 3000
error: { [InvalidRegistrationCode: The provided registration code was invalid.]
name: 'InvalidRegistrationCode',
message: 'The provided registration code was invalid.',
status: 401 }
Error: Can't set headers after they are sent.
Here's the client output:
vlcj: (DefaultMediaPlayer.java:183)
addMediaPlayerEventListener(listener=com.amazon.alexa.avs.AVSAudioPlayer$1#4b3a4950)
There was a problem connecting to the Companion Service. Trying again in 2 seconds. Please make sure it is up and running.
[DEBUG] joining on thread Thread[Timer-0,5,com.amazon.alexa.avs.AVSApp]
There was a problem connecting to the Companion Service.
Trying again in 2 seconds. Please make sure it is up and running.
The AVS launcher opens too, and when I record something and send it I get:
com.amazon.alexa.avs.AVSException: 403 Invalid Access Token
The instructions mention (at the very bottom of the reference guide) that I need to:
Please register your device by visiting the following website on any system and following the instructions: https://localhost:3000/provision/************** That URL is supposed to pop something up once the companion service but that hasn't happened.
Any thoughts on how can I fix this?
I was following a good document Project: Raspberry Pi + Alexa Voice Service at https://github.com/amzn/alexa-avs-raspberry-pi . It describes all steps very well.
Please take a look at the following steps:
3 - Getting started with Alexa Voice Service
3.1 Register for a free Amazon Developer Account
3.4 Register your product and create a security profile.
6 - Enable Security Profile
This thread on the Amazon developer forums seems related: http://forums.developer.amazon.com/forums/thread.jspa?threadID=11327&tstart=0
Quoted response:
There are a number of potential issues causing that error.
You might be sending an invalid scope. Are you sending "alexa:all" as
the scope? Or, your security profile might not be correctly linked. Is
it selected in the dropdown on the developer portal?
Are you getting an access token from the companion service, or is the
text box blank? If you're not getting an access token, check that your
device serial number matches between the companion service and the
java client. If you're getting an access token, the problem is more
likely with your security profile.
You should also look at these threads to see if they're helpful...
(links removed due to reputation requirement)
If that doesn't help, you'll probably have more luck asking the AVS team directly on their forum site.
Today out of the blue my WEBApp started failing in the login. I am authenticating the users against LDAP. The Web App is hosted on a Windows 2003 Server with Django 1.6.1 and Apache 2.2 and mod_wsgi.
The error is
ERROR : 18/02/2015 01:52:17 PM : result(3) raised
NO_SUCH_OBJECT({'info': "0000208D: NameErr: DSID-031001CD, problem
2001 (NO_OBJECT), data 0, best match
of:\n\t'OU=EU,DC=osud,DC=corp'\n", 'matched':
'OU=EU,DC=cosud,DC=corp', 'desc': 'No such object'},)
I checked on http://docs.oracle.com/cd/E19957-01/816-5618-10/netscape/ldap/LDAPException.html#NO_SUCH_OBJECT and it says this
NO_SUCH_OBJECT
public static final int NO_SUCH_OBJECT
(32) The entry specified in the request does not exist.
At http://www.python-ldap.org/doc/html/ldap.html it says this
exception ldap.NO_SUCH_OBJECT
The specified object does not exist in the directory. Sets the matched field of the exception dictionary value.
But none of these realy apply in the situation. And after like 2 hours the login started working again. There was a restart of Apache Server in between but not sure if that can contribute to this.
What else can i do to get to the bottom of this issue? Any more logging that can be added to get more information?
I had the same problem and it was related to my base DN: OU=name,dc=some,dc=random,dc=organization
The CN of my OU got changed and my python script started to show the same error message:
ldap.NO_SUCH_OBJECT: {'info': "0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:\n\t'DC=some,DC=random,DC=organization'\n", 'matched': 'DC=some,DC=random,DC=organization', 'desc': 'No such object'}
Try running the query using some LDAP client (ldapsearch and Apache Directory Studio are my favorites) and compare the results.
I hope it helps,
Server Spec:
Wordpress 3.0.1
PHP Version 5.3.8-1+b1
MYSQL 5.1
Apache/2.3.16
Linux
The Problem
Simple really. A website that I helped to build and install a while back has just been transferred to a new host. The front end of the website isn't presenting any issues, but when I try to login to the admin area, I get a 501 'Unsupported Method ('POST') error.
I'm a bit lost, my guess would be it's a server config issue, but are there any specific wordpress issues that might be at fault?