Fuck Facebook API , fuck Facebook SDK.
Basically fuck everything related to Facebook

So sometime back I was working as an android developer for a startup managed by a guy who wasn't much of a techie. The team wanted a share image to facebook option in the app, which required FB SDK integration into the app, which in turn will increase the app size and request more permissions. On discussing this with them and asking for the app secrets, they said that I'm being ridiculous, and denied me from giving the app secrets, citing the reason 'They're called secrets for a reason'.

Reading the Facebook PHP SDK documentation today to make a custom feed on a site. The documentation tells you how to do absolutely everything. Which is great in theory, but means you have loads to read to find the small bit you need.

Turns out I didn't need the SDK after all. Used simple curl request instead.

Everybody is criticizing Microsoft for leaving too much legacy code in Windows, etc., but let me tell you that I prefer 100% that and have lifetime backward compatibility than having to deal with Google bullshit.

Google sucks ass.
It's one of the most dev unfriendly company on this planet (along with Facebook).

You can't fucking change BASIC stuff in Android SDK every fucking version.
You just can't!

You can't use a system of "PERMISSIONS" each developer has to set in its application and each user has to accept during the installation, that a few versions later become USELESS... because "Hmmm… no, It's not enough, let's make a new privileged permission that makes the old one fucking worthless".

YOU FUCKING, TOXIC, BASTARDS.

It's my app, my code, my device, my fucking conditions. If I want to install viruses on my device, I should be able to do it.
I shouldn't have to call fucking Sundar fucking Pichai fucking CEO of fucking GOOGLE.

USERS != BABIES.
DEVS != CRIMINALS

We are the reason you have a fucking job, fucking food on your fucking table.

I want a fucking GOD_MODE permission in the next SDK, assholes!

You can't REMOVE fucking "Android.OS.getSerial()" making it only for system apps.
It's not sensible data… and if It's in your opinion, you've already created a "android.permission.READ_PHONE_STATE", so what else do you want, fucking asshole?
Right, you want to introduce "android.permission.READ_PRIVILIGED_PHONE_STATE" to make obsolete the other one, son of a bitch!

I don't fucking use you're garbage Google Play Store, no worries! I won't upload my app on your servers, bitch!

They've created a monopoly in the industrial space (PDAs) and they keep making fucking wrong decisions every single year.

My job is already stressful, why you can't just stop making it worse? fml

Is it wrong to expect some widespread documentation from a $350 billion company to properly document a key part of their upgrade path for a new SDK version? beware any Android devs upgrading from API 3.X to 4.X on the Facebook SDK.......you'll want FacebookSdk.setLegacyTokenUpgradeSupported(true); before your call to initialize.....

Screw Facebook SDK Docs.

Facebook SDK

Does anyone else hate the Facebook SDK or is it just me?

You have to jump through so many hoops and get different tokens for different end points. Why???

Take a lesson from Google. Get an API key and send a get request. Simple.

Shame on you Facebook Developers!

I’m neither messy or anal coder, but whenever I push something to production I make sure to handle all debugger warnings... I don’t think it’s perfectionism, rather good practice, makes important bugs easier to find. ;)

A single Facebook SDK Framework has 70+ unhandled warnings, trivial things, could be fixed in a half day...

I had to use ‘inhibit_all_warnings!’ flag literally for the first time, not to get frustrated every time it gets updated :/

P.S Not to mention I had to change the dependency manager because (with the newest update) they have written themselves out of compatibility with the one I was using... C’mon guys. Not cool.

Why the hell is facebook sdk documentation so fucked up?! It doesnt explain anything! And on top of that google doesnt help much either. Grrrrrrrrrrrrrrrrrrrrrr

I need to work with Facebook SDK for a login and in my work they have not wanted to install Composer on my computer for several months. Will they think I'm going to hack the Pentagon with that? 🤦🏾‍♂️

Today we picked an old (6 months old) iOS project back to add some features. We clone repo and run `pod install` to pull the dependencies.

There seems to be a bug with FBSDKCoreKit (facebook SDK) and the only solution is to delete the Podfile.lock

if we do this, it will pull the new version of every dependency, and the public API of each dependency is broken. Meaning we have to spend about 18 hours+ just to make this shit compile.

Fuck this shit!!

This is a continuation of my previous rant about admob being not very informative when it comes to invalid traffic and the resulting restriction in ad delivery.

I then wanted to use admob mediation to hang in facebook ads. My app is written with Xamarin.Forms.

So first I needed to make some facebook configuration - create an account, let my app review, create some ad placements and other shit. I came to the point where I had to put in a link to my privacy policy and the link could not be accepted due to some SSL fuckup -.-'

I then found out that there is an issue with my SSL Chain. With the help of whatsmychaincert.com I solved that issue. Little side note here: I have limited knowledge of that stuff and my cousin helped me set up my homepage so I had no idea what I was doing. Did a snapshot and luckily I did not needed that as everything worked :)
This took me around half an hour just so I can paste the fucking link to activate my app in facebook developer portal.

After that I made the whole mediation configuration shit - not an issue as google documented this quite well but it took some time.

Now comes the shitty part. To use admob mediation you need adapters to the other ad network. I found a nuget package with exactly what I needed just to find out that it is outdated. So I pulled the repo and saw that this thing is an aar binding library. Never did that stuff so I read some docs again. Updated the package and consumed it in my app.

The google docs then said "Use this mediation test shit to check if you did everything correct before going prod" - aar binding nr. 2 (but I am now familiar with that :P). This thing then told me that facebook ads could not be loaded because the SDK version is outdated -.-' SDK version comes from another nuget package which is referenced by the first aar thingie. I tracked that thing back to a repo where I found out that they are indeed totally behind. So I downloaded the aar, made a binding lib and bound that to my first aar binding lib as that depends on this.

Put that all back in my app - tested mediation and fucking finally after 6 hours everything comes together! all lights are green and things work.

Sorry if this is not quite a rant but it was quite a journey and I just had to share it.

Fuck Facebook and fuck their Graph API. Would it fucking kill somebody over there to write actual facts about request limits instead of that pretentious bullshit about their CPU resources and just how cool and awesome it is for me to use.