-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
investigate auction end event not emitting without specifying timeout #3813
Comments
hi - publisher here (Granite Media). to follow up, we use:
we assumed it would default to a timeout of 3000ms. most things behave normally on our page as a result of this. however we just discovered that auctionEnd never fires. this is now a new problem because UserID usersync callback seems to be based on this event firing. if we explicitly call a timeout, then everything fires and works as expected.
lemme know if you need additional info |
Hi @khatibda, Do you have a URL available with the setup (and issue) you mentioned above so I can review further? Thanks. |
@jsnellbaker. i don't have a live url at present because we resolved why including the timeout property explicitly. are you able to reproduce locally? if not, i can look into pushing a test page with the bug still present. |
I was trying some ways to artificially induce the scenario, but I was seeing the auctionEnd event emit successfully during those attempts. If you can put something together that reliably reproduces the behavior, I would greatly appreciate it. |
@jsnellbaker here's your test page: notice how the auctionEnd doesn't get logged. if you toggle into the control bucket (with the timeout property explicitly included in requestBids), you should see auctionEnd get logged. |
@khatibda Thanks for providing the test pages. I believe I found the cause for the auctionEnd event to not fire. Basically, the event is hidden by a flag that's only active when you pass a function in the In the case of your first page, it's only passing the I tried to look through the code in your build file ( |
@jsnellbaker you are absolutely right, and we should have micro-tested this double difference. in my local environment, if we include bidsBackHandler and not the timeout property, it works (auctionEnd fires). if we include only the timeout and not the bidsBackHandler, it doesn't work. so this confirms your theory. that said...does this mean any pub who doesn't include bidsBackHandler isn't firing auctionEnd? isn't that most pubs? seems like a more specific problem, but also a bigger one! |
I'm not sure that it's most pubs. That said, I'll take a look at the logic and see if it can be handled better. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
test page is coming down, this feels like it was reviewed/addressed. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
…ompletes (#3841) * move auctionEnd events so it always executes * remove some commented code
…tion completes (prebid#3841) * move auctionEnd events so it always executes * remove some commented code
…tion completes (prebid#3841) * move auctionEnd events so it always executes * remove some commented code
Type of issue
If you requestBids without specifying a timeout and the default 3 second timeout is used, no auction end event is emitted.
The text was updated successfully, but these errors were encountered: