Summary: Dynamically loading standard parameters list from server. If fail, ball back to the default list
Reviewed By: KylinChang
Differential Revision: D46922765
fbshipit-source-id: c66d1466beb9e6eb1fb4122d664c4c68d82f01f1
Summary:
**Context**
As previous diffs D46705940, we enable `ProtectedMode` to filter non-standard parameter of App Events in client side. But without those params, the MACA matching cannot be done in server, so we need to move the MACA rule matching to client side as well.
**In this diff**
- Add new feature `FBSDKFeatureMACARuleMatching`
- Add new class `MACARuleMatchingManager` and add to the AppEvents' configuration
Reviewed By: KylinChang
Differential Revision: D46779149
fbshipit-source-id: d12ac3b6be2cd173fdd5023d096c1ad1478cd2f8
Summary:
**In this diff**
- Implement the filter method of ProtectedModeManager.
Now the standardParameter list is hardcoded in FBSDK, will change to dynamically load in the future.
Reviewed By: KylinChang
Differential Revision: D46708165
fbshipit-source-id: 6984dec83ae578e87e8df2871c28ab93a2a989ba
Summary:
New diff copy from D46668428
ProtectedMode is a new feature added in FBSDK, in order to filter the non-standard parameters in AppEvents that will be sent to the FB server.
**In this diff**
- Create ProtectedModeManager class stub
- Add protectedMode to the AppEvent configuration
Reviewed By: Nathaaaalie
Differential Revision: D46705940
fbshipit-source-id: e3f164c7d3c9996232b3e8d12c51128494f8cef5
Summary: This fixes https://github.com/facebook/facebook-ios-sdk/issues/2168 , app events are sent in main thread and publishing ATE didn't happen in main thread. That may cause app events flushing waiting for ATE publishing in encodedDeviceInfo and thus lead to ANR issue. We should make ATE publishing in main thread as well.
Differential Revision: D46326000
fbshipit-source-id: 28bf4cab8e5035ede740056c1eae4984095fa101
Summary:
We optimize the CAPIG config loading in this diff. We don't load the CAPIG config every time we log CAPIG event, but only load the config if:
1. Last refresh timestamp is over 24 hours, or
2. CAPIG config doesn't exist (e.g. loaded config is not valid)
We also add a flag to mark whether we're loading config now, if yes, then we just add the callback to the callback list and wait for the config loading completion. In order to make those thread-safe, we create a serial queue and put the operations inside the serial queue.
Differential Revision: D45035238
fbshipit-source-id: d69216bab9935549750b726e9894bcb61c64b937
Summary:
We need to have config loaded before we sended CAPIG events. Previously the install event logging happens at the same time with config loading and that causes we'll miss install events. In order to fix that,
1. we add `load` function which loads the config and it'll execute completion blocks after we load the config
2. in the function `recordEvent`, we'll call the `load` function and put CAPIG event logging as callback block to `load`
Differential Revision: D45034581
fbshipit-source-id: 33af95049985a26d5daf524dc23aac5435799d40
Summary: We'd like to flush events if AEM campaign id is found
Reviewed By: wx0165927473
Differential Revision: D44314208
fbshipit-source-id: 35a570ce4b5b32df16cfdca3ab5e8192dc260246
Summary:
Add AEM Shield to protect AEM Auto Setup:
- Disable Auto Setup if exception is found
- Send crash reports if exception is found
Differential Revision: D42860772
fbshipit-source-id: f61e60eb5bde373b220f343724d4639d9505d74b
Summary: Add GK control for Auto Setup so we can turn on\off Auto Setup remotely
Differential Revision: D42735249
fbshipit-source-id: 6d0c1f504fa207c77df0131f8b84689a3118960c
Summary: Add AEM Manager as part of configurator so that FB SDK can config the AEM Auto Setup
Differential Revision: D42669713
fbshipit-source-id: 4c1bcfa2bec0394e31943583bd88d43b9f74690f
Summary: These tests were flaky before now but seem to be failing in CI (only) every time.
Reviewed By: KylinChang
Differential Revision: D42723774
fbshipit-source-id: 18fc61b547231e4932569da96186989a1fd3342b
Summary: These tests are being skipped due to changes in Xcode 14.1 that produce new and different PNG data
Reviewed By: joshlevitre
Differential Revision: D41112236
fbshipit-source-id: aaec3a550c37614a62a0e7cd1243e64a2ec208e5
Summary: When configuring the shared app events instance before configuring settings, the settings app ID is nil because its info dictionary provider isn't configured yet. This change makes sure that settings is configured before all other types since so many components rely on it.
Reviewed By: jawwad
Differential Revision: D40694989
fbshipit-source-id: beb4c362ff2af539497e1f235da1c97b530dc0da
Summary: The Stack Overflow link was set up as facebook.stackoverflow.com. This redirects to the "questions tagged facebook" link at https://stackoverflow.com/questions/tagged/facebook. However it would be better to navigate to "questions tagged facebook-ios-sdk", so the https://stackoverflow.com/questions/tagged/facebook-ios-sdk link feels more appropriate.
Reviewed By: josueBrizuelaXD
Differential Revision: D40681706
fbshipit-source-id: bcb1436ca1a33035bfa712f53b4cf77daea837e9
Summary: Might as well try to wait a bit longer if it prevents the test failing.
Reviewed By: samodom
Differential Revision: D40648425
fbshipit-source-id: 2ee79f29c81c4cb340d299f876dcb3d08ba13312
Summary: Podfiles won't be updated since they are generated, but FBSDKTVOSKit.podspec is not (even though it will be removed soon)
Reviewed By: samodom
Differential Revision: D40645524
fbshipit-source-id: c896e3031d7296ed676a65017416cec9febe0de9
