-
Notifications
You must be signed in to change notification settings - Fork 66
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
Parameter: "auction_signals" are not delegated properly to generateBid #131
Comments
Yes, that is correct.
I set up similar code, but I can't reproduce your issue. I am seeing
Thanks for sharing this feedback; the lack of debuggability in the JS sandbox is something we are aware of and are investigating how it can be improved.
Agreed that this naming is inconsistent for the on-device auction flow. In the Bidding & Auction server (B&A) flow, these fields are named more consistently. We're currently in the process of updating our documentation to focus more on B&A auctions. |
Marking as closed due to inactivity, please re-open if you would like to continue the discussion |
Can you please let me know how do you check the content if auction_signals? since doing console.log is not working, do I have some why of viewing the data? It still doesn't work for me. I tried 6 parameters and 7 parameters. It doesn't work in either way. |
I assume that when sending: setAdSelectionSignals it translates to: auction_signals in generateBid.
As a side note: the naming inconsistencies are confusing and make it hard to track.
This is my Android code:
When I add the following code to generateBid I get no ads selected. Since I have no way of debugging the values of parameters, I can only assume that the value doesn't exist:
The text was updated successfully, but these errors were encountered: