I followed the instructions in the android tutorial and registered 2 native android apps in facebook. I got the ID, and so far as I remember, I put the key in as well.
I'm having errors with it now, so I'm trying to get back in and verify that I put the correct value in for the key...but I cannot get to any page that holds that info. Most links that I've followed so far just take me back to my facebook "Your pages" page, which has my account page, and a page for each of the two apps I've already registered. No link anywhere in those app pages takes me to where the key value is registered.
Even trying to create another app entry, via the tutorial, and following this link:
https://www.facebook.com/developers/createapp.php
just takes me directly to:
http://www.facebook.com/browse/admined_pages/?id=1000.....
I can't imagine how this could be any more frustrating....
Found it. It was under known "bugs". Apparently they allowed people to create business facebook accounts, and register apps under those accounts...and then regretted doing it, and so silently disabled all app access through those accounts. Yay, thanks guys. Here is the url that describes the problem and where to go to assign your apps (via the ID) to your regular-human facebook account. http://developers.facebook.com/bugs/133607873418215
Related
The app can redirect you to the FB page in question and get you to press the like button. Trying to understand if that can be done quicker. Tks
No, that is not possible.
Facebook allowed liking certain object types in the name of the user via API until a while ago - but it has been removed since, simply because the feature was abused too much.
And Facebook pages could never be liked via API, that has always been possible via the official Like buttons only.
I have a application and i have facebook page for the same.now whenever a user clicks on Use app(call to action) button on android device whether it is facebook android app or user is logged in from browser I need to open my app installed in user's phone.
I have searched so much but came across some old posts as facebook has introduces applinks.org meanwhile.
So I am not getting how to do this thing.
When you're setting up the Call To Action button on your page, you need to select App:
Then you will fill in a URL using your app's custom URL scheme in the Deep Link box (that's what actually launches your app on the visitor's device), and the package name of your app in the Package Name box (I believe Google uses this for verification purposes).
If you haven't set up a custom URL scheme yet, this Facebook docs page explains how. That will take care of opening the app (myApp://), but if you're wanting to go to a specific piece of content (myApp://path/to/content), then you also need to follow these directions.
What controls the Twitter access rights?
Is it the Twitter application as defined in my Twitter dev account?
Is it the Twitter Android API ?
Is it the TwitterLogin plugin info provided by Fabric.IO?
Is it a combination of these?
Is it something else?
Using Twitter as a Way to Identify User
All I want to do is use the Twitter OAuth which is provided by FabricIO and the TwitterLogin infrastructure so I can identify a user. In other words, let the user sign on using Twitter. However, I don't need or want more access to their account.
However, as you can see in the image below, the app seems to gain far more access to the user's Twitter account than I need.
Possible To Change?
Is it possible to change this so it is very limited? If so, where would I make those changes?
I just found the settings in my twitter dev account and it resolves some of this, but not all. However, maybe this is all it is even possible to control??
Go to https://apps.twitter.com/ (it'll take you to your twitter dev account).
If you have more than one app, choose the app you want to change.
Click the [Permissions] Tab.
You will see something like the following images:
Mine was set on Read & Write (2nd choice)- Image shows where I have now selected the Read only choice.
Click the [UPdate Settings] button and you get the odd screen that follows:
That made me think I hadn't chosen the correct choice (read only).
Finally, after a few minutes I refreshed the app settings web page and saw that it was on Read Only.
I then tried logging in using my Android application again and it now looks like the following:
Now, it cannot tweet for the user nor can it add users. It still seems a bit intrusive though, just to use it for Authentication.
I've created an android app that will post information to a user's wall. I went through the steps of creating the app in facebook, using the key to create the hash. It has gone well, and on two of my devices, I can post the info to whatever facebook account I log into. Once signed in, it doesn't ask me to again.
However, when I gave this to some other people to test, they are getting an authentication error. It's along the lines of "android key mismatch, your key doesn't match your application settings."
I've tried to get into the facebook app page for my app, to check settings there...but whenever I try to get there through the Facebook developers app page, I get redirected to my regular facebook page with "Your pages", and it lists the apps I've created there. But none of those pages lead back to the app setup/key page.
That's just kind of a side note...the real question is why does posting work fine for me, but not someone else who uses the same app?
Turns out I had the wrong key value stored in facebook. For some reason it was letting me post, but no one else could. I got the new key value from the same keystore I sign my apps with, and now it works for everyone else.
I'm having some problems with facebook integration on my android app. I've looked at the examples that come with the api and i can do the things shown in those ok. But i'm having problems with other things such as getting single sign on to work properly, authentication across multiple activities in the app and loading a facebook page (non-api call) without being asked to log in again.
Anyone have examples that show these?
When making API calls, you usually need to include the access_token parameter that was issued when the user authenticated. This is how facebook knows who you are when you make requests.
Similarly, when loading facebook pages (not using the API), you have to remember to send the cookies Facebook sent when the user logged in. Normally the browser keeps track of these automatically, but in your program or app you might have to handle them manually.
I don't have experience with Android specifically, and I don't know what you're using to load and render facebook pages, but knowing how facebook is keeping track of logged-in users should give you an idea of where to start. A google search or two should get you on your way.
Go to facebook.java class and change package name com.facebook.katana to com.facebook.katanaaa or any one of your own choice. This worked for me .