Hi Senseijayrome,

I’d verify the Git link in two places before pushing anything.

In Vercel, open the project → Settings → Git and confirm it shows the exact GitHub repo and production branch you expect, usually main. In GitHub, also check that the Vercel GitHub app has access to that same repo.

For the first deployment, the usual path is:

1git status2git remote -v3git branch4git push origin main5

If Vercel is connected correctly, a push to the production branch should create a production deployment. A push to any other branch should create a preview deployment instead.

Before pushing, I’d also check:

• Framework Preset: Next.js

• Root Directory: only set if the web app is inside a subfolder

• Build command / install command: leave defaults unless your app needs custom commands

• Environment Variables: add any backend/database keys to the correct Vercel environment before deploying

If this started in v0, note that v0 usually works on its own branch and then opens/merges a PR into main. After that merge, Vercel should deploy from the connected production branch.

Since you mentioned Expo/React Native too, I’d keep that separate from the Vercel web deployment. Vercel should deploy the web/Next.js app; Expo native builds are normally handled through the Expo workflow, not Vercel.

If a push does not create a deployment, the most useful screenshot would be Project Settings → Git showing the connected repo and branch, with private details hidden.