Corona SDK facebook.logout() not working - facebook

I have the same issue as described here: Corona facebook.logout() when the Official Facebook app is installed on device
The answer says that this is by design, but lot's of apps allow you to logout of Facebook and log back in as another user. Any idea why facebook.logout() doesn't do what the function implies it should do?

As a user of the Facebook native app, I would be highly agitated if another app I ran logged me out. I've been working with someone in the Corona forums asking the same question (Perhaps it's your post) who's building a Kiosk app, so I can see a need in that circumstance to want this feature. But given that mobile devices are highly tied to individuals, this is not a behavior that most people would want to see.
The Corona SDK facebook.logout()'s purpose is to disconnect the Corona SDK app from Facebook, cancelling the access Token. It was never intended to terminate the facebook app's user login.

Related

Facebook has blocked logins for my Meteor app because I'm not using a native SDK. How to resolve?

I manage a few Meteor-based apps that use the Facebook login functionality provided through accounts-facebook.
For one app, a week ago, Facebook emailed me saying this app was in violation of their Platform Policy, and that I had to respond to the email to prevent logins from being shut down within a week. Specifically this was the offensive clause:
Platform Policy 8.2: Native iOS and Android apps that implement
Facebook Login must use our official SDKs for Login.
I immediately responded, but (of course?) got no response from Facebook. And, yesterday, I got another email saying Facebook logins have been blocked for this app.
I updated to the latest version of accounts-facebook, appealed the block, and got a response:
We have reviewed your iOS and Android apps and they are still in
violation of the Platform Policy 8.2: Native iOS and Android apps that
implement Facebook Login must use our official SDKs for Login.
So, does this mean that all Meteor apps can get their Facebook login restricted at any time?
How to resolve this?
Today, Facebook went further, telling me that:
Your app has been restricted for creating a negative user experience
that is in violation of our Platform Policies.
Your app cannot be installed by new users.
What are they smoking?
But, whatever they are smoking, how do I resolve this?
I've sent them an email, twice, explaining that, like tens of thousands of others, I'm using the off-the-shelf Meteor package for allowing Facebook logins to my Meteor app. But, all I get back are canned responses that don't respond to my bafflement.

can people see Facebook IOS app on their facebook?

I've created an IOS app as a Facebook Developer. So my question:
Are people able to see the app when they go into their Facebook - like in the Browser? Or are Facebook IOS apps only something that you can see in the actual app on the iphone/iPad that I'm creating?
Depending on whether the Facebook developer configured a canvas facing site will show what the end user will see.
Any application made by a third party once set to public in app settings can be viewed by anyone.
If you app is made for iOS then either the user will see a misconfigured webpage or dialog asking whether the user wants to send to mobile. All of this of course depends on how the the developer of the application sets everything.
See the documentation for detailed information
https://developers.facebook.com/docs/facebook-login/v2.2

How does Facebook attribute a mobile app installation to a specific Facebook Mobile App Install Ad?

There are several questions on SO that touch on this, but the KEY question I need answered is this:
How does Facebook attribute an installation of a mobile app to a specific NewsFeed Mobile App Install Ad? Corollary: In the Facebook Insights dashboard, is the Mobile App Installations tab recording JUST installs derived from Mobile App Install Ads? Or is this capturing ALL installations?
It seems that the PublishInstall method is called every time the app is installed (assuming the Facebook SDK is integrated). How do I know Facebook is ONLY counting installs derived from the ad?
If anyone can source to something that would be the best, but an answer from knowledge would be great too.
Thanks!

How to authenticate a person who has facebook but not the facebook app on iOS device?

I am creating an app on iOS and i came across a scenario if a person does not have the facebook app installed but has Facebook. how does the game app handle that. you can only play the game if and only if you have facebook account?
You can use Single Sign On in Facebook.
So that the facebook will authenticate its user through facebook app if its installed otherwise through the safari.
Here is the Link also here.
Happy coding :)
If you targeted the older versions (below ios6) use Graph API.
If you targeted for newer version (ios 6 and above) use the native method

App Store can accept this flow or not

I have integrated Facebook functionality into my applications. By using the link https://github.com/facebook/facebook-ios-sdk, I have integrated the Facebook. In this application, at the time of login, it's opening Safari and at the same time the application is going to the background and then after login again it's coming back to the application. My intention is that this flow can accept the application store or not.
This is the official Facebook iOS SDK and many apps in App Store already use it. So you can use it inside your app.
Also, the flow in your question is exactly what the documentation of the library describes and is, again, used by apps that are already in App Store:
If the device is running in a version of iOS that supports multitasking, but it doesn't have the Facebook app of version 3.2.3 or greater installed, the SDK will open the authorization dialog in Safari. After the user grants or revokes the authorization, Safari redirects back to the calling app. Similar to the Facebook app based authorization, this allows multiple apps to share the same Facebook user access_token through the Safari cookie.
So, yes, there is nothing wrong with this flow.