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?
App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
61–70 of 446 posts
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#62Given how protective Apple is about the experience of apps on the App Store and this happening the second time, I'm surprised they have not come up with a way to prevent this from happening. Also, a monolithic SDK should not exist in this day and age.
Indeed, and if the FB SDK (as used by the Spotify app among others) does in fact call home, it might violate Apple's TOS and give rise to rejecting those apps on the App Store. I'm not up to date with Apple's policies, but wasn't Apple specifically rejecting apps that seek to establish a platform within Apple's platform? Now if Apple are going to play hardball on this one is another question alltogether.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#63How is Apple not addressing this? This seems like a pretty glaring hole in their tightly controlled environment. If the SDK is injecting code, shouldn’t that be an explicit permission?
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#64Waze, a google owned app for the past 4 years, crashes because of the FB app.
WhatsApp, a Facebook owned app, will not give you read access to your own chat database - it’s encrypted. But they have an arrangement with Google where it’s will back up unencrypted to your Google account (though, Google won’t let you retrieve it ... only the WhatsApp app can)
Everything about this duopoly, their cooperation and lack of competition stinks to high heaven.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#65Workaround for users: Enable airplane mode and disable WiFi, or block facebook domains Workaround for developers: Go to Facebook Developer page > Analytics and disable automatic Events.[0] Apparently this doesn't solve the issue for everyone. Issue in Facebook's tracker: https://developers.facebook.com/status/issues/17391881029111... [0] https://github.com/facebook/facebook-ios-sdk/issues/1427#iss...
Do you know which domains one would need to block?
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#66I use a non-Facebook login on Spotify and the app crashes right there. How is this even possible, even less acceptable from Spotify point of view?
It's not acceptable. None of the apps broken on my phone require Facebook features for core functionality. Downtime happens, but downtime due to your non-essential & user-hostile ads/tracking/social SDK? These companies deserve every single cent of lost revenue.
the sdk initialises itself just by being included. this is why the crash happens on startup. even if you only use it for login, it will still crash.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#67Earlier quoted context omitted.
... so if the app including the SDK has permission to access location data, the SDK could be passing that location data to Facebook?
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.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#68Earlier quoted context omitted.
that's not the only purpose of the SDK, we're using it for social login (login with Facebook).
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, which may use the web-view Login dialog. On iOS, only kiosk apps may use a web-view Login dialog.”
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#69I use a non-Facebook login on Spotify and the app crashes right there. How is this even possible, even less acceptable from Spotify point of view?
It's not acceptable. None of the apps broken on my phone require Facebook features for core functionality. Downtime happens, but downtime due to your non-essential & user-hostile ads/tracking/social SDK? These companies deserve every single cent of lost revenue.
If the last time this happens is anything to go by, a lot of apps have the FBSDK to facilitate their "Log In
with Facebook" functionality. The issue is that you have to include a monolithic SDK that initialises itself without your control just for simple functionality like that.
IMO, blame Facebook.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#70How is Apple not addressing this? This seems like a pretty glaring hole in their tightly controlled environment. If the SDK is injecting code, shouldn’t that be an explicit permission?
It's "inside" the application and the code is injected at build time, by the sounds of it.