3 ms·
Considering the SDK is setup to run, and crash, with just being linked in and not even a single call, FB should be responding. Their app is clearly phoning hom
by kevin_b_er 6y ago
Considering the SDK is setup to run, and crash, with just being linked in and not even a single call, FB should be responding.
Their app is clearly phoning home during the self-initialization. For a period of time it was breaking massively, then suddenly not. That means some orders from the home server were bad and causing the SDK to crash the app out. All during a secret self-initialization the developer can't temporarily take out.
- onion2k 6y agoApple should be responding. If a third party library is leading to massively downgraded performance of user's devices, Apple should be warning developers that their apps could be rejected if they don't guard against the broken behaviour. The fact developers can't do anything is a good reason not to use the SDK, not just to accept the problem. If this continues to happen regularly Apple will start taking measures to stop the problem - and banning apps is a (very unlikely) possibility.
- kevin_b_er 6y agoApple could ban the hooking trick the SDK uses to run w/o an initialization call and prevent app updates. Then either FB fixes their nonsense or developers remove the SDK.