You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great and legit question. Short answer: yes and it does sound pretty odd, but:
The value of skAdNetworkHandling is late being processed here.
As you can see, its value (true) is being stored into variable which is named deactivateSkAdNetworkHandling which now sounds like it makes much more sense.
Later that value is being passed to the native layer where if it's set, it will be used to actually deactivate SKAdNetwork handling natively.
It's set if it's not -1, which is default value for not set nullable boolean (more info) which skAdNetworkHandling is. Which technically means that even if one would assign false to skAdNetoworkHandling, it would technically cause native deactivation to happen. But since no code path is setting that, it should be that only setting it to true (the call to the method and assigning from your initial comment) causes disabling on the native level.
Definitely a confusing path in the code thanks to poor naming of things on our end and something that should be changed (and it will be changed soon).
Hopefully this clears things up for you and thanks for the question.
If you still have some questions / comments, feel free to ask.
adjustConfig.deactivateSKAdNetworkHandling() makes skAdNetworkHandling = true. is it correct?
The text was updated successfully, but these errors were encountered: