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
My expectation here is that when the prop values for the adUnit and targetingArguments changed the ads would be reloaded with the new prop values.
What appears to happen is the original slots are destroyed and new ones are created with the values for the original slot that was generated (located in the registeredSlots object in the manager). Therefore the targeting of the new ads is not representative of the current set of props.
Is this behaviour expected / a bug? and is there a way to reload the slots with the updated information?
Thanks
The text was updated successfully, but these errors were encountered:
Hi @jaanauati looks like this issue with DFPSlotsProviding not re-rendering when updating the targetingArguments prop is still happening, so none of the targeting arguments are updating. The workaround is not working for me, do you know if the DFPSlotsProviding was ever re-rendering / working as expected? I tried to use version 0.10.0, but the issue seems to be the same. I had a quick look and it seems the context is updating correctly.
Im setting up the
DFPSlotsProvider
with theautoReload
prop set to{ adUnit: true, targetingArguments: true}
My expectation here is that when the prop values for the
adUnit
andtargetingArguments
changed the ads would be reloaded with the new prop values.What appears to happen is the original slots are destroyed and new ones are created with the values for the original slot that was generated (located in the
registeredSlots
object in the manager). Therefore the targeting of the new ads is not representative of the current set of props.Is this behaviour expected / a bug? and is there a way to reload the slots with the updated information?
Thanks
The text was updated successfully, but these errors were encountered: