Facebook developer Account kit settings not displaying - facebook

Im trying to configure account kit. but the settings are not displayed, why is that ?, I have tried to log from 2 devices but still same screen.

That was a temporary issue and should be fixed now :)

Same is happening here. I've already tried to access it with different facebook accounts and with different projects, and nothing happened.
I'm also receiving errors in my recent registered apps, when tying to send the SMS. But it still works with the old ones.

Related

Adsense banners showing transparent background

Believe me that I've asked this in Adsense forums (Spanish AND English), and also checked the following resources and questions:
1 - 2 - 3 - 4
I have an AdSense account that actually works with AdMob. We see successfully ads on Android, but I can't see them for web. We can create in AdSense new ads without a problem and we let pass even more than 2 months to ads to set themselves up, but nothing changed.
Still, the answer I get from ads is a 200 status with the following HTML content:
<html><body style="background-color:transparent"></body></html>
Giving bounty since none has been able to resolve it, nor Google Forums or Stackoverflow!
EDIT
We've checked with a brand new account and it works!! Our original account is not banned though and it's serving ads for AdMob, but the problem comes with AdSense (for web)!
I had almost the same problem once. With the settings I made Google was not able to get advertisement for my page. See the answer:
https://support.google.com/adsense/answer/113262?ctx=tltp&hl=en
The solution (for me) was to add a new unit and a completely new channel as well. If You check the If no ads available option You can choose from 3 options:
Collapse the ad unit, otherwise show blank space (default)
Collapse the ad unit, otherwise show colour
Show other URL
If the problem persists you should send a feedback message including the URL, the exact description of the problem. This is maybe an internal problem in Googles algorithm (as if it is not able to find ads for you).
Important: Have you checked from different browsers, other machines and Google accounts? The algorithm behind the whole AdSense motor is relying on those information heavily. (It means that if You do not see ads on your site, it still could show some to others.)
Edit: If You tried to use a newly created unit and it did not work, I suspect a google bug and I am mostly out of ideas. In my case this solved the problem, but if You are unlucky with it You really should use an other account if possible.

Parse iOS facebook login fails

I am using parse facebook login for new users of my app. Most users are able to use it without a problem and I have successfully tested all Facebook login scenarios. Some users, however, report that when they press the login button they see brief activity indicator and then nothing happens. In code, no error is registered but the user is not brought beyond the login page to the app's initial screen. The problem resolved if the user deletes the app from their Facebook app settings and then tries again. Has anyone else experienced this and/or found a solution? Thanks
Not sure if this ever got resolved for you.
There are multiple possible causes for this of course including your own code. However, we've seen a similar issue with 2 causes / solutions.
UX-wise we detect multiple failed logins (typically with no error code) and then pop a notification telling the user how to solve. Still digging for a code-level solution that'll solve either of these issues permanently (if you found one, please post!) but hope these help & let you know you're not crazy.
Issue #1: User is logged into multiple Facebook accounts from the same device (e.g. a primary account and an org or 2ndary account).
Fix #1: Have user log out of all Facebook instances (app, safari, iOS settings) and then log back in.
Issue #2: User has rejected Facebook permissions.
Fix #2: For iOS, make sure Your App is toggled on in Settings -> Facebook -> Your App

facebook ads not install tracking

I have this really odd problem. The bosses in the office decided to do facebook tracking by using the [FBSettings publishInstall:<appIDhere>] in the app delegate. This works because the graph.facebook.com/<appID>/activities, etc are called, and Facebook returned true.
However, the problem is that this is NOT showing up in the dashboard. The app_activate shows up just fine, it's just that the app install is not showing at all.
So, my questions are:
Why is it that the install is not read correctly? The call is made and facebook response. Why is it that it's not showing up in the dashboard?
Does facebook do any other filtering? For example, if I delete the app and then reinstall, should the app be counted to have installed twice? In this case, the call to graph.facebook.com/ is made twice to send the MOBILE_APP_INSTALL activity. After this, does facebook do any other filtering? e.g. they remember device tokens, etc?
I am not quite sure how facebook differentiate using the URL scheme. I presume that this is to differentiate people who upgraded compared to people who installed. How does the fb<appid> help as a URL Scheme?
Thank you in advance for all your help.

Facebook Login Error iOS Application

My iOS application allows me to login using my own facebook account successfully. But when I send it on test flight to a friend, the app downloads but when he presses connect to Facebook (which works on my simulator and personal device), it won't let him log in. Doesn't even give him the option to, just spits out an error (com.facebook.sdk error 2). What am I missing? What would cause it to work for me, but not for others? I'm just looking for a general answer here because I followed all the facebook tutorials and I can't imagine what kind of thing could be going wrong.
I just figured out the problem. Should have been SUPER obvious, but being new to development I didn't realize I needed to change the sandbox setting to disabled in order to allow others to access facebook through my app.
This error pops up when your app is not authenticated properly.
You need to keep your BundleId the same at all places.
Change your bundleId in the app that you have registered on Facebook as com.asdad.casd instead of < teamId >.com.asdad.casd

iOS and Facebook Graph API: Inconsistent authorize issues

I'm using the official FBConnect library for iOS and trying to get it working in my iPad app. Here's what's strange: when my friend logs in using the call to authorize:permissions:delegate, everything works fine: the dialog asks for his authorization to connect to Facebook, the fbDidLogin delegate method gets called, all is well.
However, when I try to login, the dialog never changes. The keyboard is dismissed, the password field is cleared and it just sits there. The issue is the same in both the simulator and on the device.
Here are the things I've checked and triple checked:
My login name and password are correct. If I do put in the wrong password, an "invalid username/password" message appears, and that isn't happening.
The application is not in sandbox mode.
The Application ID is correct (my friend can login without problems).
Some additional information:
Original application was created by my friend.
I created a second FB app and put in the new Application ID
My friend can login with the new Application ID
I can log in to neither.
This appears to suggest that there is something different about my friend's account, rather than the app itself.
We've been banging our heads together on this for a couple of days now. What could be causing this behaviour? Why isn't an error being generated?
Edit: It seems there are a lot of people affected by this, so in the interest of trying to find an answer, I've added a bounty.
There appears to be a server-side problem with Facebook logins as noted here:
http://github.com/facebook/facebook-ios-sdk/issues#issue/95
People have said that if they change their password on Facebook they are subsequently able to log in using the Facebook-iOS-SDK downloaded from github. Obviously that is a poor long-term solution and would be unacceptable in an app released through the App Store. On the bright side, there seem to be reports of similar login problems logging in from apps on other platforms as well.
Update: Facebook has a bug filed on this subject that can be viewed here:
http://bugs.developers.facebook.net/show_bug.cgi?id=13199