MGTwitter is not working - iphone

I don't want default twitter to open because it should be compatible with ios < 5 also .
I've used MGTwitterEngine. But it doesn't post tweets. Before few days it was working fine with ios5 too. But now it's not working. I think twitter demo url is depreceated , or not supported with ios5 & 6. What could be the reason? while posting something to twitter the request gets failed & I'm gettiing following error :
Error Domain=HTTP Code=404 "The operation couldn’t be completed. (HTTP error 404.)
Any help would be appreciated !!

Twitter deprecated API version 1 url.
In MGTwitterEngine.h line 40 change
#define TWITTER_DOMAIN #"twitter.com"
to
#define TWITTER_DOMAIN #"api.twitter.com/1"
More info https://dev.twitter.com/discussions/10803

Modifications...
1. Change the TWTTER_DOMAIN in the MGTwitterEngine.m line 40 (pat posted).
2. Chenge the OAuthConsumer.h remove all OAuthconsumer strings.
3. Chenge the HTTP url with SA_OAuthTwitterEngine.m line 65~67, add the api string before twtter.com

Version 1 of the API is now deprecated. This document may describe an outdated version of the API. Please move to Version 1.1 of the API as soon as possible.
Go through this document.
https://dev.twitter.com/docs/api/1.1/post/direct_messages/new
Point to be noted
Api format should me json
Api version v1.1
sender and receiver should follow each other.
Example Request
POST : https://api.twitter.com/1.1/direct_messages/new.json
POST Data : text=hello&screen_name=rajneesh071

Related

Socialite laravel 5.4 Facebook Provider

i have a problem here maybe sameone can help me: i install the Socialite pakcage to my laravel project and in start it work perfect with facebook , google and linkedin provider. But now it get always this message when i try to connect with facebook , and other provider connect perfectly.
What's wrong ?
ClientException in RequestException.php line 111:
Client error: GET https://graph.facebook.com/v2.8/me?access_token=&fields=name,email,gender,verified,link&appsecret_proof=5fbda0d218f94cb8024712269c053f0186d360efd82cd358b588eaf621e0c79c
resulted in a 400 Bad Request response:
{"error":{"message":"An active access token must be used to query information about the current user.","type":"OAuthExce (truncated...)
I fix the problem !
You need the make same changes in vendor/laravel/socialite/src/Two/FacebookProvider.php file
See here:
github socialite
composer update will fix it by updating the laravel/socialite version
Oh, so I'm not the only one. Good. Waiting on the answer, I've lost like at least 60mins trying to figure this out, I'm quite sure it's gonna be something Facebook related. They're killing their 2.2 api, I guess, today, maybe they messed up something. :/

Dropbox API error status codes

I was using Dropbox API, but could not find a standard list of status error codes to respond to such as here: https://api.imgur.com/errorhandling#400
Imgur offers an awesome list. Does dropbox docs have any place like this?
Check out the Error Handling section of https://www.dropbox.com/developers-v1/core/docs.

The New Facebook Request Dialog

http://forum.developers.facebook.net/viewtopic.php?id=88364 Tried this,but how can i access the 'data' field from request receiving end.
You should look at the latest documentation. The post you are looking at is really old and I believe refers to the 1.0 version of the Request Dialog. Facebook release 2.0 early this year and has updated it twice since then.
https://developers.facebook.com/docs/reference/dialogs/requests/
https://developers.facebook.com/blog/post/569/
There announcement of 2.0 https://developers.facebook.com/blog/post/464

Vkontakte Audio Search with HTTP API

Sorry for my English. I know very little English.
I am trying pull data from here : http://api.vk.com/api.php?api_id=2539386&count=200&v=2.0&method=audio.search&sig=c2b83d95d3d5914de0aa6ae7ca1c1007&test_mode=1&q=beatles
c2b83d95d3d5914de0aa6ae7ca1c1007 = md5->141080534api_id=2539386count=200method=audio.searchq=beatlestest_mode=1v=2.0mysecretkey
But return to me : "Incorrect signature: ifame/flash authorization"
Where is error ?
Should've read the API documentation first, the solution to your problem gets explained in pretty much the first line about the Audio Search method. You're getting an error because you're not authorized yet. You need to authorize your app first with rights with bitmask 8. More info about the Audio Search method | More info about the application rights bitmasks
You are using old method my dear :) Use like this:
https://api.vk.com/method/audio.search.xml?access_token=TOKEN&q=QUERY
Replace TOKEN with your access token... Replace QUERY with your search term
More info

facebook chat on the iphone using xmppframework

Well i started of by following all the instructions here:
http://code.google.com/p/xmppframework/wiki/FacebookChatHowTo
I used the recommended fork of the facebook api and tried the latest from:
https://github.com/facebook/facebook-ios-sdk/
My problem starts with the following error:
< failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl">< not-authorized/></failure>
The error is a reply from facebook to xmppframework s response to a authentication challenge. The response that is made by the iphone is base64 encoded msg when i decode it i find 2 of the values are null:
api_key=(null)
and the
session_key=(null)
This is obviously the reason facebook is returning that error. But the problem i have is i cant seem to find any where to set these values in the framework. Besides i think the session_key should be pulled in from facebook anyway.
I guess what i want to know is a couple of things.
Has any one got the xmppframework working with facebook on a iDevice?
If you have got it working did you have to stray from the path of the instructions on http://code.google.com/p/xmppframework/wiki/FacebookChatHowTo ?
do you know of any other method to get facebook chat working on the iphone?
Any suggestions or help for my current dilemma would be appreciated. Happy to share my code if you want.
cheers
I wrote the Facebook integration for XMPPFramework. The api_key and session_key, come from a call to auth.PromoteSession. Facebook is trying to deprecate that call, so to enable it, you must follow step 7, in the HowTo:
Under Migrations, change Disable Deprecated Auth Methods from Enabled to Disabled and Save Changes.