Opinie (Connect to Remote Agents with ADK and the Agent2Agent (A2A) SDK)

There are error and problem in the steps as teh line numbers were wrong and also forbidden error coming up.

Aayush G. · Sprawdzono 22 dni temu

I was not able to continue the session further as stuck at second for the usersession tried multiple but no

Praveen G. · Sprawdzono 22 dni temu

time limit was less

Vishal R. · Sprawdzono 22 dni temu

i have completeed and deployed the agent multiple times,ensuring the server is runnning and accessible.Despite this,the progress is not being reflected for the deployment task.This seems to be a technical issue with the lab validation system

Sumedha M. · Sprawdzono 22 dni temu

Miroslav D. · Sprawdzono 22 dni temu

Maitrii M. · Sprawdzono 22 dni temu

auth user error

Gurusharan B. · Sprawdzono 22 dni temu

Alexandru C. · Sprawdzono 22 dni temu

worst experience in my entire learning journey

Ak P. · Sprawdzono 22 dni temu

Stuck to this part. Even though I changed it from 0-8 it doesn't work Note: As before, if you get a Forbidden Error 403, you may have multiple accounts signed into your Incognito session. Try incrementing the value of the authuser value at the end of the URL, for example changing it from authuser=0 to authuser=1. authuser=2, etc. In production you could handle this with a service account creating a Signed URL.

Mark Samuel N. · Sprawdzono 22 dni temu

Ketan D. · Sprawdzono 22 dni temu

i dont want to give even one star, so many flaws, i tried my self to rectify the errors but still 1 hour is not enough worst

Nadanesh K. · Sprawdzono 22 dni temu

Chetan G. · Sprawdzono 22 dni temu

karthik g. · Sprawdzono 22 dni temu

a2a step 3 is not able to detect cloud run

Sam W. · Sprawdzono 22 dni temu

this has a bug

Deeksha C. · Sprawdzono 22 dni temu

There are too many issue wiht the AUTH always throwing me 403 forbidden error eve though i have tried musltiple things

Akash M. · Sprawdzono 22 dni temu

Yes

Pramod M. · Sprawdzono 22 dni temu

lab task 2 and 4 failed because of some glitch

Rohan B. · Sprawdzono 22 dni temu

Khemraj P. · Sprawdzono 22 dni temu

Using adk web --allow_origins="*", solved 403 error

Vithurabiman S. · Sprawdzono 22 dni temu

I encountered a blocking issue in this lab that prevented completion despite following all instructions carefully. The ADK web server started successfully, but every attempt to send a message resulted in a consistent 403 Forbidden error from backend endpoints (e.g., /run_sse and session creation APIs). I verified the following multiple times: Correct lab-provided account was used (no personal account interference) Project ID was correctly set and active gcloud authentication and application-default credentials were configured Vertex AI API was enabled Environment variables (GOOGLE_CLOUD_PROJECT, GOOGLE_CLOUD_LOCATION) were set Clean sessions were used (incognito, multiple browsers, fresh lab restart) Despite all of this, the issue persisted across multiple lab restarts. The provided troubleshooting note about "authuser" is not relevant to this failure point, as the error occurs before any browser-based image preview step. This appears to be an environment or lab configuration issue rather than a user error. Request: I would appreciate either: Credit for lab completion, since the issue is reproducible and blocking, OR Guidance or fix for this specific error This lab consumed significant time (~14 credits), and I made a genuine effort to debug systematically before reporting. Thank you.

jay p. · Sprawdzono 22 dni temu

Sarath T. · Sprawdzono 22 dni temu

Kundan K. · Sprawdzono 22 dni temu

Oken K. · Sprawdzono 22 dni temu