We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hello everyone,
I have an issue when I use this two methods, I get an 401 error Other method have no problem.
I directly store the token that i get from a webservice. The token app is in Read, write, and direct messages
The text was updated successfully, but these errors were encountered:
I have the same problem. Any luck fixing it?
Sorry, something went wrong.
No for the moment I use my own webservices in php, which can make the call with the same token
For anyone who has this problem, the twitter api path has changed.
It's building a path like: https://twitter.com/statuses/update.xml
What you want is https://api.twitter.com/1/statuses/update.xml
In MGTwitterEngine.m you have to set:
line 40 - #define TWITTER_DOMAIN @"api.twitter.com"
line 1023 - NSString *path = [NSString stringWithFormat:@"1/statuses/update.%@", API_FORMAT];
Hopefully this project will live long enough to support those of us that have to support users on iOS4 for the time being
No branches or pull requests
hello everyone,
I have an issue when I use this two methods, I get an 401 error
Other method have no problem.
I directly store the token that i get from a webservice. The token app is in Read, write, and direct messages
NSUserDefaults *defaults = [NSUserDefaults standardUserDefaults];
[defaults setObject: data forKey: @"authData"];
[defaults synchronize];
}
return [[NSUserDefaults standardUserDefaults] objectForKey: @"authData"];
}
The text was updated successfully, but these errors were encountered: