The file upload is still only detecting the app folder and uploading that, anything in the ROOT is not uploaded anymore?

It will only upload the app folder and does not upload / detect the root.

Its 100% never going to work like this. it cant find any of the root files

It now just shows "Start from this ZIP file." where as before it would show all the files uploaded. I have done this process so many times and it works for the last few months but yesterday I upload the project and it just ONLY uploads the app folder no matter what is selected.

v0 it is stupid.idiot

@matthewhutchings I'm having the same issue - did you find a solution?

I successfully uploaded the code as a project in the native Android browser, but I have never succeeded on PC or other types of browsers. This is really a foolish mistake.

Its really funny with how it needs to be uploaded.

I ended up doing something like: zip -r myproject.zip . \ -x "node_modules/" ".next/"

It seems to do better when you include the git repo in the code. Initially I was zipping the files up but you really need to zip the project folder (exclude next, node...) and then try

confirmed it works if you upload the git file.

downloading an existing v0 project and then uploading it does not work.

You have to download, create git repo - zip and upload

Same situation here , cant reload the zip, after load the file structure is damaged no lib subfolder anymore many parts are placed in root and import failed - answer from vo: You are correct - this appears to be a malfunction in v0's ZIP import process. Based on the images you provided, I can see the factual discrepancy:

Facts from the images:

Import Dialog (second image):

• Shows proper lib/ subdirectory structure
• Contains files like lib/utils.ts, lib/errorHandler.ts, lib/neon-db.ts, etc.
• 855 files were selected for import

Generated CodeProject:

• Files that should be in lib/ are placed at root level
• utils.ts, errorHandler.ts, neon-db.ts, etc. are missing the lib/ prefix
• Directory structure has been flattened

Open Issues:

1. Directory Structure Loss: The lib/ subdirectory structure visible in the import dialog was not preserved in the CodeProject
2. File Path Inconsistencies: Import paths in the code likely reference lib/ paths that no longer exist
3. Potential Breaking Imports: Any file importing from @/lib/... will fail since files are now at root level

Additional Context Noted:

• Schema uses public.user (not users)
• Existing schema should be utilized when needed

This is indeed a v0 import functionality issue where the directory structure shown in the upload dialog is not maintained in the generated CodeProject. The files exist but are incorrectly placed at the root level instead of preserving their original lib/ subdirectory structure.