Replies: 1 comment
-
just seen the updated specs, all the message stuff wasnt there when I saw it some weeks ago.. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello A2A SDK Team,
I'm developing an agentic system using the A2A SDK together with ADK, and I'm trying to implement push notifications as described in the A2A specs. Specifically, I'm including the push notification configuration object within the message send params.
However, when I debug the server (using the default request handler), I notice that although the push notification config is present in the incoming request, it does not seem to be available in the handler logic. After the request is parsed, the config appears to be moved into a new configs property within the params (e.g., params.configs.pushNotificationConfigs or similar), but this is always None when I inspect it.
Additional context:
My client is a custom C# client, not the Python client from the SDK.
Questions:
Is there something I need to configure in the SDK or the handler to ensure the push notification config is properly passed through and available?
Is there a recommended way to access the push notification config in the handler, or is this a known issue with the default request handler?
Any advice or example code for making sure the push notification config is correctly handled and stored with the task would be greatly appreciated.
Thank you for your help!
Best regards,
Leo
Beta Was this translation helpful? Give feedback.
All reactions