Is ShareKit going to stop working for Facebook sharing come 11th October 2011?
As I understand it the current version (0.2.1gm1) of ShareKit uses the REST api, which is based on the old iPhone SDK (facebook-iphone-sdk) and according to today's blog:
On October 11th, apps using the old JavaScript Library (FeatureLoader.js) or the old iPhone SDK (facebook-iphone-sdk) for authentication will no longer be able to authenticate users until these apps switch to OAuth 2.0
Or does it already use OAuth 2.0, so no changes are needed?
Just a little confused as to whether I need to update my apps in advance or not - thanks!
Related
Our iOS app uses official iOS Facebook SDK (latest version) to handle user login and getting user friends. This is the only way of interaction with Facebook platform. We do not make any direct HTTP requests to Graph API, etc.
But when I open Facebook developer portal, I get a warning: "API Graph v2.8 will be deprecated on Apr 18, 2019 ...".
How shall I react to it? I checked that API Graph integrated into the Facebook SDK is later than 2.8. Can I safely ignore the warning then?
As long as you don´t use any features that are deprecated with v2.8, you can ignore it:
https://developers.facebook.com/docs/graph-api/changelog/
...and if the SDK uses a newer version, you are safe anyway.
We've migrated to the latest LinkedIn IOS SDK which only supports single sign-on (SSO) authentication, in conjunction with the official LinkedIn mobile application. Our app works really well with this, however Apple will not approve our latest version, because it requires the LinkedIn app to be installed for the authentication to work.
We need a solution which handles the scenario when the LinkedIn app is not present, to use web authentication, however LinkedIn are very specific stating Mobile SDK-enabled applications require the official LinkedIn iOS app to be installed on the device to function properly" https://developer.linkedin.com/docs/ios-sdk - The Mobile SDK was released in July, so presume we are not alone in having our app rejected by Apple approvals.
Could you test for the presence of the linked-in app:
if it is not there: implement OAuth2 directly through your app
if it is there: use it or your OAuth2 implementation (which you'd probably err on the side of using their app for the link-ability between any features of the app you may need in yours).
Thereby avoiding the REQUIREMENT to have the app installed.
Researching for this I did find:
Mobile vs server-side access tokens
Presently, there is no mechanism available to exchange them. If you
require tokens that can be used in both the mobile and server-side
environment, you will need to implement a traditional OAuth 2.0
solution within your iOS environment to acquire tokens that can be
leveraged in both situations.
from: https://developer.linkedin.com/docs/ios-sdk-auth
which suggests that authentication away from the app is supported.
Pleased to confirm that the solution kindly suggested by Madivad of using the new LinkedIn SDK if the LinkedIn app is installed and when it's not reverting to traditional OAuth 2.0 works fine. Apple are also back on our Christmas card list as they approved this latest version today within 40 minutes of submission:) Thanks Madivad for helping out with this.
I'm gonna make an native iOS app with Swift 2 and Xcode 7. The users should login using LinkedIn and OAuth 2 but I'm wondering how I should begin to set this up. I don't have many experience with OAuth 2.
Is there a good tutorial or a sample app? I saw the Ray Wenderlich post but that comes with an existing project. I want to build an app with LinkedIn login from scratch.
EDIT
I want to use the LinkedIn login to get the user's connections and send them notifications. I was researching this and I found some pages that said that connections can't be retrieved from the new LinkedIn API, is this true? It is not possible to get someone's connections from LinkedIn in a native iOS applications?
You should start with LinkedIn guide for LinkedIn and OAuth 2 .
But still if you need a sample for Authentication with OAuth 2 here it is .
For your second question related to the connection yes Linked have made changes but the API is still available but for the partners .
If you are an existing LinkedIn partner, these changes will not impact your existing partnership or the associated APIs that your partnership allows you to access.
If you are experiencing issues as a result of the May 12th changes, please reach out to your LinkedIn Business Development representative immediately.
For further details you can see Developer Program Transition Guide.
Check out this repo, I did this swift pre-2.0 but it shows you the basic algorithm. You can do it the with your secret hard coded or fetch it from the server. The key is getting the oath header just right which is a huge pain
https://github.com/GregPrice24/SwiftStream
Check this out: https://github.com/jeyben/IOSLinkedInAPI
I used this repo and successfully implement LinkedIn integration in my App. It is in Objective-C but you can use Cocoapods and import them as Frameworks and use in swift2 with no trouble.
Note: As of the 12´ May 2015 LinkedIn applied restrictions to API usage for all non partners: See: https://developer.linkedin.com/blog/posts/2015/developer-program-changes
So you can only get the basicprofile at the beginning, but you can apply for the partner program to get those extra information such as connections here: https://developer.linkedin.com/partner-programs
I work on a legacy iOS app, which uses Facebook SDK to let user login and publishes on user's behalf likes and posts on the wall. It requests email, publish_actions, user_likes permissions.
The app already has a valid app token and worked fine with Facebook SDK v3.13, pointed to Graph API v1.0.
Recently I have upgraded it to Facebook SDK v3.23 with Graph API v2.2.
Facebook's upgrade guide (https://developers.facebook.com/docs/apps/upgrading#v1tov2) says:
Once you are defaulted to Graph API v2.0, you should test all possible
features to ensure full functionality. <...> If your app is fully functional
after defaulting to Graph API v2.0, you need to go through Login
Review before April 30th, 2015.
What happens if I refuse to go through review?
Will the older ("v1.0") / newer ("v2.2") builds of the app be still functional after 30/05/2015?
Will the users be able to log in and like/post/share?
V1.0 will be gone completely after April 2015, and all permissions that need review will stop working if they did not get approved.
I am using the following java script api for facebook connect http://static.ak.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.php
Then i received this email from fb
Dear Developer,
As part of our continued efforts to migrate all apps to OAuth 2.0, we opted in all apps using the new JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and reverted at 1:30pm because we noticed that your app has not migrated. Please ensure that you have set the oauth param in FB.init to true and that you are using FB.getAuthResponse to obtain the access token.
Read more in the OAuth2 migration announcement, updates to the new JS SDK blog post, or our JS SDK docs.
But i did't updated my fb connect implementation and it is still working fine. I am not sure will this effect my fb connect in future? and secondly why my implementation is still working fine? Any help will be really appreciated.
You should use the new version as soon as possible. I've been dealing with Facebook and their various APIs for four years now. This is the most warning they've ever given for deprecating anything, so this is big for them. Upgrade your websites ASAP. :)