App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m (github.com)

Article summary

An app is suddenly crashing on startup due to an issue with the Facebook SDK, specifically the FBSDKRestrictiveDataFilterManager.m file. The crash is happening for 100% of users, with over 1400 crashes reported in a short period. The issue appears to be related to a server-side change. The app's developers are looking for a solution to resolve the issue and prevent further crashes.

Main themes

• Facebook SDK issues
• App crashes and stability
• Developer responsibilities
• Third-party SDK risks
• Login and authentication methods
• Data tracking and privacy concerns
• Software development and testing practices

What commenters say

• The Facebook SDK's poor quality and lack of testing are to blame for the frequent crashes and issues.
• Developers are often pressured to prioritize speed over quality, leading to problems like this.
• The Facebook SDK is essentially spyware and should be avoided due to its tracking capabilities.
• Dropping support for Facebook login is not a viable option for many apps due to the number of users who rely on it.
• Facebook's policy requiring the use of their official SDK for login is overly restrictive and forces developers to include potentially problematic code.
• Alternative login methods, such as server-side OAuth implementation, could be used to avoid the Facebook SDK altogether.
• The responsibility for ensuring the stability and security of apps lies with both the developers and the providers of third-party SDKs like Facebook.
• Some commenters believe that the benefits of using the Facebook SDK outweigh the risks, while others argue that the risks are too great and the SDK should be avoided.