Live data from Hacker News

App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

github.com

91–100 of 446 posts

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#92
post #73

Earlier quoted context omitted.

How do you do that? At OS level with a setting? Networking changes?

I use an app called AdBlock https://apps.apple.com/app/apple-store/id691121579?pt=425087... It creates a local VPN that sets up a local filtering DNS. I just added the following domains to the block list: facebook.com fbcdn.com fbcdn.net fbsbx.com fb.com

Great tip, thanks. Edit: This worked like a charm. Goodbye facebook, welcome back Spotify.

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#93
post #39
post #7

Earlier quoted context omitted.

It would be nice to have a complete list of apps that include this spyware so we can avoid them.

Or you can block the DNS to be sure. facebook.com fbcdn.com fbcdn.net fbsbx.com fb.com instagram.com

I already do that, but it's good to still know which companies intentionally distribute malware so you can avoid giving money to them.

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#94
post #71

Earlier quoted context omitted.

Do you know which domains one would need to block?

facebook.com fbcdn.com fbcdn.net fbsbx.com fb.com instagram.com WhatsApp can work without these, but maybe a smaller subset would suffice. NextDNS[0] for iOS can be used for the blocking. [0] https://nextdns.io/

connect.facebook.net graph.faceboom.com sdk.facebook.com

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#95
post #41

Earlier quoted context omitted.

Except, you know, when does a developer ever have a choice? You are asked to put the SDK in and you do it...

this, combined with a wrong past technical decision that we can not change it instantly. unfortunately it's not as easy to fix mobile bugs as it is on the web, as you have to both pass the approval process and wait for the full rollout to clients. in our case, it's just a wrong decision, we don't use it for tracking. also, if you use facebook login, the terms and conditions force you to use their SDK (which automatic…

Just to clarify, when I say "the developer" I don't necessarily mean the person writing the code: I mean the organisation developing the software, so they definitely have the choice.

In terms of the person writing the code, they can certainly push back. Being asked to add the Facebook SDK is either a red flag enough for him/her to do so, or they don't mind. In either case, they've made that choice.

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#96

Earlier quoted context omitted.

You can implement OAuth entirely server-side without any client support beyond displaying a web view. No need to include spyware and the approach is reusable for any OAuth provider.

You can’t, it’s against their policy, if they catch you they’ll revoke your access. developers.facebook.com/policy/ 8.2 (which states “Native IOS and Android apps that implement Facebook Login must use our official SDKs for login.” This has a help icon next to it that opens a dialog on their site that shows a couple pictures and then explains “Android apps should use the default login behavior defined by the SDK, whi…

A generic login experience on the web (where the entire login flow is implemented in the browser and the login button just redirects to Safari, including for email/password accounts) should work around it. You can provide technical reasons as excuses for why it's impossible for your app to include edge cases for each login provider to be included natively in the app.

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#97
post #73

Earlier quoted context omitted.

I use an app called AdBlock https://apps.apple.com/app/apple-store/id691121579?pt=425087... It creates a local VPN that sets up a local filtering DNS. I just added the following domains to the block list: facebook.com fbcdn.com fbcdn.net fbsbx.com fb.com

That's very interesting. Does Android have anything similar?

Not sure, but you can use something like NextDNS to achieve the same. It’s basically a “pihole in the cloud”:

https://kennis.cc/public_uploads/0caeb8d4.png

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#98
post #73

Earlier quoted context omitted.

I use an app called AdBlock https://apps.apple.com/app/apple-store/id691121579?pt=425087... It creates a local VPN that sets up a local filtering DNS. I just added the following domains to the block list: facebook.com fbcdn.com fbcdn.net fbsbx.com fb.com

That's very interesting. Does Android have anything similar?

Android has tons of these apps. Cuz its Android. An app exists for everything.

Check out Blockada. (Non-root)

Adaway (root and non root phones)

Adaway requires version 5.something for non rooted devices. Anything less than version 4 is only for rooted devices.

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#99
post #67

Earlier quoted context omitted.

Not only could it do that, but it also totally does do that

Didn't they also use to home in information about surrounding bluetooth devices? When iOS 13 beta dropped, half of the apps suddenly asked for bluetooth permissions because Google/FB SDKs attempted to use it on app launch.

Not sure about Bluetooth devices, but the Facebook SDK definitely phones home with some system data and generates an unique identifier on first launch which is then included every further interaction the SDK has. Both of these enable fingerprinting and persistent tracking.

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#100
post #58

Can confirm that blocking Facebook on my iPhone makes these crashes go away. All in all I might leave that block up permanently as nothing going to those addresses does me any good

How do you do that? At OS level with a setting? Networking changes?

You can also do this with NextDNS[1] which gives you a "denylist" of domains to not resolve. All you need to do is change your nameservers to the ones they give you (or they also have a VPN option, I think?)

[1] https://nextdns.io

Post reply on HN