I am using Oath authentication in my ios app for twitter integration.
It was working fine earliar but now when I authenticate user then it sends me on this page. Whats going wrong. is there any change in API?
I think you are using older API that stopped working So now you have to go for new Solution.
Apple Introduced Social Framework that Allows Facebook, Twitter sharing without doing much more & with less efforts.
use This.
Hope this will help.
Related
I am new in application development and recently while working in my application which is in PhoneGap (Cordova 2.5) i need twitter login for my app.
I have googled for this and what I got is
"https://github.com/phonegap/phonegap-plugins/tree/master/iOS/Twitter"
but in github all the info is not given so that I can run my app for twitter login .
Is there anyone who could help me to create twitter login in PhoneGap??
Do some reading on OAuth. Implementing OAuth authentication on your own is not that bad. Although, Twitter uses OAuth 1, not OAuth 2, so that might make it a little more tricky. If I had more PhoneGap experience, I could could provide more direct answers, but I've only done native development. Best of luck.
I have one problem regarding OAuth integration in iPhone App.
Can anyone help me how to integrate OAuth 2.0 with facebook in iPhone ?
I have referred so many sites about OAuth but I haven't got satisfied answer yet. I referred this question of stackoverflow. There is one good option about ShareKit. But my client wants only OAuth 2.0.
I downloaded framework from google code. I integrated it in my application. But How to use it ? Without guidance I can't implement it in proper way.
I have got stuck between my application and 0Auth 2.0 since last 3 days. Please can anyone give me idea or demo project or any another tutorial ?
Rather than implement OAuth for Facebook, make use of the Facebook iOS SDK which makes handling Facebook Auth and Requests much easier. You can read about it and download it here... http://developers.facebook.com/ios/
I just done a research
This post will really help you
Also please look at the below posts
iphone-facebook-oauth2-graph-api
OAuth and Facebook iPhone SDK
The framework you mentioned in your post is not for OAuth 2, but for OAuth 1.0a.
You can try the OAuth2Client we developed for talking to the SoundCloud API. It's build against draft 10 of the spec. I'm not sure which one is used by Facebook. Unfortunately the spec is not final yet and over the years different services adopted different drafts of the spec.
If you're able to argue with your client I'd try to convince him to let you go with the official iOS SDK. This gives you many benefits like automatic token refresh, single sign on via the official app & much more.
I am integrating this Twitter API in my project.
http://mobile.tutsplus.com/tutorials/iphone/twitter-api-iphone/
This is running well with my App. but I want to sure that is it valid or authorize API for Twitter ? Will I not get any problem in future or from app store ? Although this is looks good and it is also asking for CnsumerKey and COnsumerSecretKey.
Please know me.
Thanks in advance.
This is a valid Oauth API.You won't get any problem in app store.
I am looking for the SDK to integrate Twitter into my iOS App. I have done research, and seem that MGTwitterEngine is what most people recommend. However, MGTwitterEngine only provides access to the Twitter API, but not the UI.
I also looked a few iPhone app with Twitter integration, such as SCVNGR, FriendsAroundMe, Hashable, they all have the same login page. However, I couldn't find out what SDK these apps use.
I wonder whether there is any SDK release (from Twitter would be the best), which includes both the SDK with standard UI implementation, and some demo code.
Thanks for your advice.
Steve
The login UI for these apps is probably a UIWebView. I say probably because I haven't seen those apps that you've mentioned. The login for Twitter is usually handled in a UIWebView, because Twitter requires OAuth. Since the login is done in a UIWebView, Twitter actually provides that UI.
I would recommend ShareKit for basic Twitter interactions, like posting. ShareKit handles the UIWebView for you. edit: ShareKit (0.2.1) seems to have some memory leak issues. Use at your own risk.
I have a project that builds oAuth and streaming on top of MGTE. The project includes a demo that does authentication in a web view, and streams tweets to a table view.
https://github.com/TimShi/TSTwitterEngine
You can integrate Twitter via Twitter API which requires OAuth. And OAuth requires web-browser in any form. All the other parts can be done without web-browser, but authentication requires it.
You can hack those OAuth web pages in background via UIWebView's JavaScript interface, but the log-in page changes often. And your users will experience log-in trouble until you update hacking algorithm.
In fact, Twitter offers another authentication method called xAuth. You can authenticate completely in background without browser with this protocol, but you have to be approved about using of this protocol from Twitter company via direct contact. I don't think regular startup service can acquire the approval.
I don't think OAuth offer any better security or protection, but this is the only card which I can use without trust from Twitter.
The official Twitter Kit SDK support was discontinued in 2018.
As an alternative solution for displaying Tweets in your app without Twitter Kit, you can render Embedded Tweets and Timelines within webviews using Twitter for Websites.
Check out this link:
https://medium.com/#musmein/rendering-embedded-tweets-and-timelines-within-webview-in-ios-e48920754add
I am building a twitter application that is currently using the classic login instead of OAuth. I don't know how to use Oauth to implement login.Please anybody help me to provide some help regarding how to login through OAuth login
If you want to be done with it as fast as possible, use Ben Gottlieb's Twitter-OAuth-iPhone library. If you want to know exactly what happens, plan a few days to read all you can about OAuth, and then several weeks to implement.