fix: race condition with requestManager for tam & prebid bids #127
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.
Description
This fixes an issue when using both Prebid and Amazon TAM (APS) with React Advertising.
When multiple
AdvertisingSlots
call theactivate
function at the same time to request a new ad, they all use the samerequestManager
object to keep track of whether the Prebid and APS bids have returned. Because therequestManager
values are used as conditional to control when an ad gets refreshed, this creates a race condition between the different ad units. The first ad unit to get both bids back gets refreshed/rerendered, the others don't.The fix was to give every new ad request it's own
requestManager
object, instead of sharing a global object.