Postmortem on issue #1374?

[AustinConlon]

Any chance a postmortem could be written reflecting on issue #1374?

[JCBird1012]

Time to make another one of these issues for #1427 as well (which will probably also be ignored).

[ghost]

It would be very useful to have a central document that includes:

• whether an SDK update to prevent this class of issue has been released or if a fix is planned -> this will help me prioritize upgrading the SDK.
• notes on mitigations for older versions. e.g. Is the advice to disable automatic events logging an effective mitigation?

Currently the best documentation on this seems to be the github issues themselves, but they are very noisy to sort through.

[Jumhyn]

This is especially important given that the Facebook Developer Policy for Login (8.2) requires that developers use the official SDK if they support login. It's against policy to drop the SDK altogether and implement the API oneself:

• Native iOS and Android apps that implement Facebook Login must use our official SDKs for login.

[booleanbetrayal]

@joesus - As a chief maintainer, can you provide a post-mortem on #1427 as well as #1374?

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

[CyberMew]

Was there ever a post mortem on this issue?

[AustinConlon]

No, they decided to ignore it.

[booleanbetrayal]

=[