vlad/autoreg-skills-max
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
autoreg-skills-max/skills/browser-signup-automation/references/vercel-v0-referral-signup.md

2.7 KiB
Raw Permalink Blame History

Vercel / v0 referral signup notes

Date: 2026-07-12 Target: https://v0.app/ref/03TUF8 -> redirects into https://vercel.com/signup/v0?... Script: C:\Users\User\Downloads\Telegram Desktop\bot_hybrid.py

What was changed in the script

  • Set REF_CODE = "03TUF8".
  • Added top-level HEADLESS flag.
  • Added --ref, --workers, --headless, --menu argparse interface.
  • Removed sys.argv.append("-n") because argparse then fails with unrecognized arguments: -n.
  • Added Chrome args --no-sandbox and --disable-gpu.
  • Strengthened form submit fallback from only button/Enter to form.requestSubmit() / form.submit().

Observed runtime behavior

  • Browser successfully opened Vercel signup URL.
  • Email field became visible and accepted the temp-mail address.
  • Continue with Email click logged as successful.
  • The page stayed on the email form for 60+ seconds.
  • OTP screen never appeared.

Important interpretation

This session did NOT prove the referral flow works end-to-end. It only proved:

  1. navigation works,
  2. email field fill works,
  3. initial submit interaction happens.

It did NOT prove that Vercel accepted the temp mail or actually sent an OTP.

Likely causes when this exact symptom appears

  • Temp-mail domain rejected silently.
  • Hidden anti-bot/challenge after submit.
  • Frontend accepted the click but backend refused progression.
  • The form needs a different post-submit interaction than the visible button path exposed.

Recommended next diagnostic pass

  1. Capture DOM text immediately after submit.
  2. Capture screenshot after 5s and 30s.
  3. Log all visible error banners / helper text.
  4. Swap temp-mail provider before changing the browser stack, unless the user explicitly constrained the provider.
  5. Only start OTP polling after positive evidence that the page entered verification state.

Provider-specific note — mail.tm only

If the user says to use mail.tm only for v0/Vercel signup, do not silently fall back to Gmail aliases, AnyMessage, or another temp-mail provider. Probe https://api.mail.tm/domains first and log the returned domains.

Observed 2026-07-13:

  • mail.tm /domains returned HTTP 200.
  • Only one domain was available: web-library.net.
  • v0/Vercel did not progress to OTP with that domain; treat this as a target-side domain rejection or anti-bot block until DOM/screenshot proves otherwise.

Operational rule: when constrained to a single mail provider, report the exact provider/domain status and stop at the verified blocker instead of inventing an alternate inbox path.

Known good launch note

SeleniumBase first run may spend time auto-downloading uc_driver.exe / chromedriver.exe; do not misread that bootstrap noise as app behavior.