Core: add privacyIcon to not native asset list #10259
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description of change
Added
privacyIcon
to the list ofNATIVE_KEYS_THAT_ARE_NOT_ASSETS
list in thecostants.json
file.Previously when the
privacyIcon
asset was included in a native adUnit using the legacy setup, thebidRequest.nativeOrtbRequest
created an additional asset that had no proper reference within the native ortb spec. By adding this field to the list, the asset does not get created in thenativeOrtbRequest
object.Found while investigating #10249