Facebook share dialog android return error - android

I want to share a simple link from my android app.
I followed the getting started guide from Facebook and all seem okay in my app since I can open the share dialog.
I imported FacebookSDK project and linked library
I set my appproperly (package/class name and dev hash keys)
My manifest has right permissions and meta-data
Additional infos :
I use a real device for debug
I run a test app as admin
I'm running a simple share code sample from an activity
I had troubles to generate hash keys but that post helped me. I got an error saying XXX key (different from the one I generated) doesn't match.
Then I tried the method explained here (at the end) to log another key.
Since now, I just get a toast saying "Something went wrong. Please try again."
What am I doing wrong ?

So I solved my problem thanks to another post. The problem is I was trying to generate a key outside my main (first) class.

Related

Facebook Xamarin Android app getting Content Not Found error

I'm having an issue with my Xamarin Android app returning the info below. From what I can tell I have everything configured correctly in the settings. The package name, class name and hash keys all look good.
Could there be something I'm missing?
I also posted in the Facebook Developer Community page but haven't received any responses.
Update
Should the Class Name be MainActivity? Something like namespace.MainActivity MyCompany.Android.MainActivity

Facebook Dialog Sharing issue with SDK in android(#100 invalid fbid)

I am facing one issue in publishing post via facebook app using sdk in android.
When I am trying to post something, it gives me toast message like"(#100) invalid fbid". and Log is printed as : Error: com.facebook.FacebookException: Error publishing message.
Please note: I have added Publish Permission,My FB App is visible to all Users and most Importantly,I have made a demo using same app id,package name and all and it is working there,but when I am merging that code in app,It always ends up in the error.
So,What could be the cause?Because same code,same fb app id is working fine in separate app,but not working when merged in the application.
Please suggest what should I do?
Thank you in advance.
SOLVED.There was mistake in manifest.xml...We should write android:value="app_id".I have written android:resource="app_id"..So it was error of class casting between Integer and String.

Scringo Facebook , app id logcat issues , Facebook login works with Parse SDK not with Scringo

I use parse sdk and scringo in my app , parse works fine for my login with facebook so app_id is set correctly , but when login via scringo it just shows please wait
any help !!
Logcat
Scringo(11060): You need to set the facebook app id in the manifest. See https://developers.facebook.com/docs/tutorials/androidsdk/3.0/upgrading-from-2.0-to-3.0/#login
how to go ahead with facebook sdk and scringo , the site is not informative and even the api docs dont explain much , no reply over email so i have to turn to SO for help
EDIT:
I use broadcast receiver now as per their guides , how to login correctly
http://www.scringo.com/docs/android-guides/popular/handling-login-status-changes/
What you're describing is a problem common to all Facebook libraries, you need to create an application on Facebook and get an id/key (http://www.scringo.com/docs/android-guides/popular/connect-to-social-networks/), most libraries then require that you set it in the manifest. I haven't used this library, if you want to try using https://github.com/sromku/android-simple-facebook I can provide more help (if you need it, Simple Facebooks guide is pretty good), otherwise this hopefully makes it clear what you're missing
According to their quick start guide, Scringo it turns out also has it's own App Ids which you get through a dashboard, take a look here: http://www.scringo.com/docs/android-guides/quickstart/
I had the exact same issue.
I fixed it by adding my scringo app id in the scringo.properties file under the assets folder of my project:
scringo.app.id="your_scringo_app_id"
Hope it helps.

Android Titanium App "invalid OAuth consumer key" Error

I have a problem with my first published Android Titanium App
In connection to the cloud I get this error:
"invalid OAuth consumer key"
The keys are properly septate
thanks
Mr. Andrea, Please recheck all the 6 keys in your TiApp.xml file. This issue occurs when the acs-oauth-key-production is incorrect. I've marked the keys in the first picture. You'll get the original keys from your applications as given in the second picture.
Hope it resolved your issue
The problem was on in the code, but not at the level of the server configuration, but had problems.
I created another service I changed the keys
so it all works

Android: Error when login Facebook using new Facebook SDK v3.0.2.b sample

when I using new Facebook SDK v3.0.2.b sample HelloFacebookSample, I login to Facebook but I get error:
HelloFBSample is misconfigured for Facebook login.
But I have already generate Hash key and add it to Sample App Setting on Facebook Developer site.
Is anybody get the same defect?
Or is it a bug of new SDK?
Sometimes the Key Hash generated using the method given by the Facebook Doc does not always work as advertised. I have faced this problem and so have a few others.
There are a couple of things you can do to sort it out.
First method
Follow the tutorial on this site: http://www.helloandroid.com/tutorials/using-facebook-sdk-android-development-part-1
This is a little time consuming (about 5 odd minutes I expect) but worked when I tried it.
Second Method (And I personally like this one)
Find the Util.java in the Facebook SDK and open it.
Among the first few lines of code, you should see this piece: private static boolean ENABLE_LOG = false;.
Change the false to true and run your application with your logcat (DDMD) open.
You should see an error that looks something like this:
Login failed: invalid_key:Android key mismatch. Your key
"**real*key***" does not match the allowed keys specified in
your application settings.
If this is for a testing APK, using the debug.keystore, this will be enough. However, if this is for an app signed with your release key, then follow the steps till Step No. 3 but instead of pushing the app from eclipse, create a signed APK and install that on your device. Don't forget to keep it connected with DDMS running.
This part here: "**real*key***" is your actual key.

Categories

Resources