I used the example OAuthTransitionMac,it is OK for the old auth,but when using the new OAuth it got the error
An error occurred in the stage "OAuth", error: Error
Domain=org.lukhnos.ObjectiveFlickr Code=2147418116
UserInfo=0x101e515e0 "The operation couldn’t be completed.
(org.lukhnos.ObjectiveFlickr error 2147418116.)",
I setted breakpoint and run,when using new OAuth the request token isn't successfully obtained and it got into
- (void)flickrAPIRequest:(OFFlickrAPIRequest *)inRequest didFailWithError:(NSError *)inError.
I had read the document on the http://blog.lukhnos.org/post/11275346353/flickr-oauth-support-in-objectiveflickr but couldn't solve it.
Please someone help me!
I had an issue where I was logging the user out, but I was not setting the oAuthToken && oAuthTokenSecret to nil on my OFFlickrAPIContext object when I was trying to log in with a different user. Once I set those two variable to nil, then it logged in fine and I no longer got this error.
Related
Since 6 July 2018 we have been receiving the following error when making API requests to Podio:
An exception of type 'System.NullReferenceException' occurred in
Podio.NET.dll
but was not handled in user code...
Line: PodioClient.AuthenticateWithApp(AppId, AppToken);
We haven't changed anything in our code.
This has basically just started happening. I can confirm we are using TLS 1.2.
Could someone shed some light on this issue?
We are using the libraries from here - http://podio.github.io/podio-dotnet/
Please use newest Podio .Net Nuget packages that are now published:
https://www.nuget.org/packages/Podio/
https://www.nuget.org/packages/Podio.Async/
Check them out :)
We have to forced the application to read TLS 1.2 from server by adding the code below at the beginning of the application:
'ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
But sometime the application is fail and return errors below, see screenshot attached.
Podio Errors
'2018-07-13 13:51:51.5860 ERROR Object reference not set to an instance of an object. Object reference not set to an instance of an object at PodioAPI.Podio.Request[T](RequestMethod requestMethod, String url, Object requestData, Object options). at PodioAPI.Podio.Get[T](String url, Dictionary`2 requestData, Object options) at PodioAPI.Services.FileService.DownloadFile(FileAttachment fileAttachment)'
I am getting following error from Google bigquer while doing streaming inserts:
Error message Signet::AuthorizationError: Unexpected status code: 500. Server message: { "error": "internal_failure" }
I can understand that there can few errors but the same doesn't get reflected on console as shown below:
As you can see in above, image, there are no 500 errors but yet in real there were 10 500 internal_failure errors.
Can you tell me why these errors don't refect on console & how do I ensure they don't happen?
This looks like a failiure to get your authentication token. This failure would occur before the client code even attempts to call the bigquery api, so the console you are looking at is accurately representing traffic.
I suspect it is a failure on a request to https://accounts.google.com/o/oauth2/token. Perhaps monitoring on outgoing http requests could verify this? (For example, see Getting error 500 when trying to obtain access token from authorization code and Internal_failure while getting refreshtoken using code?)
Back to the BigQuery API: when it returns an http error code 500, the error string will be one of "backendError" or "internalError". (For the curious: "backendError" is usually retriable, while "internalError" is likely a permanent failure.)
I'm trying create some users in the console. I'm getting the following error:
Authlogic::Session::Activation::NotActivatedError: You must activate the Authlogic::Session::Base.controller with a controller object before creating object
This error occurs in an after_create which only job is to send an email to the user. If I disable this after_create, everything works, but this means no email is sent.
I tried to apply a solution found here, but it didn't work:
http://www.tatvartha.com/2009/09/working-with-authlogic-in-scriptconsole/
What's going on?
Thank you
It isn't clear to me, when exactly an invalid_request error happens. Does this also happen if the token to authorise isn't valid anymore?
Thanks, udo
I don't think this is the result of an unauthorized request, for that you should be getting an '401 unauthorized' error.
It is more likely the result of not sending the proper parameters. Although the documentation says that the error in that case should be invalid_parameters, in some events an '400 invalid_request' error will be returned instead.
I am trying to use Dropbox API on iOS but I got trapped by the error when I try to use loadMetadata method.
process flow is below..
1.link (UserA)
[[DBSession sharedSession] linkFromController:self];
2.allow authorization on dropbox authorization view
3.unlink (UserA)
[[DBSession sharedSession] unlinkAll];
4.link (UserB)
[[DBSession sharedSession] linkFromController:self];
5.allow authorization on dropbox authorization view
6.loadMetadata
[[self restClient] loadMetadata:path];
But here I get the error:
Terminating app due to uncaught exception 'Unsupported Signature Method', reason:
'The signature method "(null)" is not currently support by MPOAuthConnection'
loadMetaData did work correctly as UserA but it did not work after changing user.
I doubt that the way to unlink could be not enough .. but I do not know.
Please give me any advices in order to solve the problem. Any help will be appreciated.
Migrating the answer above to a proper one.... As #yusaku posted in a comment on his question, this link has the answer: https://forums.dropbox.com/topic.php?id=94511#post-517526
Specifically, Greg K. says:
Make sure you clear all your DBRestClient objects when you unlink. If
you try to use an old DBRestClient object it will cause this problem.
Clearing the old DBRestClient should be a no-brainer, but when it's late and you're following sample code that makes it a persistent class variable, it's easy to skip a brain or two.