Today between 14:00 - 17:00 (UTC+0) %50 of the calls to the method GET me/permissions resulted in errors.
"User has not installed the application (code 412, subcode null)"
Facebook API version : 2.8
Why this error occur ?
Any answer will be appreciated.
Related
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.
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...
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,
I am attempting to setup a custom 404 error with CF10 and IIS 7.5. Previous to CF10 (and IIS 7), you can get the URL of the non-existent page via the querystring (e.g., 404;http://www.example.com/some/file.html) when the custom 404 page is processed. However, with CF10 and IIS 7.5, the querystring returns 404;http://www.example.com/jakarta/isapi_redirect.dll. Is there a way to retrieve the actual URL of the missing path, like in prior versions?
I have a workaround that I posted to the page Miguel-F commented on:
ColdFusion 10 + IIS: Non-existant URLs that are CFM files. Retrieving original URL after executing 404 page
It's not pretty but it works...
Problems with custom 404 error pages and IIS 7.5 were addressed in the latest CF10 update - Update 11. You have to re-run the web server connector once you install the update. If you do not re-run the web server connector, then the IIS/custom 404 error pages problem will not be fixed. This is the official blog post regarding Update 11 and the web server connector. The fixes introduced in Update 11 may solve your problem.
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?