Since the last update I’m not able to import a .postman_collection anymore…Can someone investigate please? Thank you
Hey @chantal-decraie 
Welcome back 
Are you able to share more details here, please?
Is it showing you an error or is in completing but you’re not seeing the Collection in the sidebar?
If it’s the second issue, could you try Clearing the Cache and reloading using this menu option?
@danny-dainton , I ran into something similar after the last update of Postman.
The system refuse to import a basic and working collection, and is trying to import forever th environment.
If I can provide something specific for analysis purpose, don’t hesitate to ask.
It looks like you are trying to import both a collection and an environment. I tried to import a collection JSON(v2) on my end, and I was not able to replicate the error.
Was this collection exported from somewhere else (outside Postman)?
FYI: We just rolled out v3 of the collection format. The v3 is in YAML and more durable, but importing v2, which is in JSON, should still work fine regardless.
I’ve just upgraded to Postman v12 and it COMPLETELY BROKE my workspace.
I see that it won’t work with v2 JSON format. It has a fix button to convert to V3.
I tried it.
But when I try to import the converted v3 collection:
TBH, this is a frustrating experience. I even tried to downgrade but I can’t even do that.
I think I’m done with this software. I’m going to migrate to Rider’s Http Client. Thank you for your service.
It looks like you are trying to do this all in the Local mode - Did you successfully connect to a git repo before this stage? Are the Collections still repo or did you pull these from the Cloud Workspace?
Hi @danny-dainton I don’t have the possibility to select “Clear cache and reload” in my collections. We’ve setup a crossteam based workspace where I had access to to write and read, but that also has been denied.
So my solution was to create my own workspace and upload it there. Nevertheless, this is not what we were expecting.
But ok, I can continu
Kr, Chantal
The Clear cache and reload option in at the top level menu for the Postman instance, it not at the Collection level.
Are you part of a Team plan and able to create shared Workspaces?
Without more visual information and any errors that you’re seeing, it’s difficult for me to know what’s happening on your side. 
I’m also having issues with the new format.
I’m able to import a v2.1.0 collection, but having a 2.1.0 collection on a git repo (Local view) it seems it stopped working (it was working before this upgrade) and even if it say it detects the collection it is not shown:
If you create new items (collections, requests, etc) it uses the v3.0 format (creates .yaml files)… but there is no way (or I couldn’t find any on how to generate a v3.0 collection from a v2.1.0)
- Export a collection still uses v2.1.0
- There is no transformer from v2.1.0 to v3.0 (GitHub - postmanlabs/postman-collection-transformer: Perform rapid conversion and validation of JSON structure between Postman Collection Format v1 and v2.)
I did the “Clear cache and Reload” and it does not help.
This version brings in the V3 collections format which wasn’t part of the previous version that you might have used when connecting to git pre V12.
I can’t see the full screen on the Connect tab, have you tried pulling in that Collection into the local view to see the migration steps?
My collection has also completely broken. Was working fine before update. Postman suggests I use AI to regenerate a collection. Tried doing so and it generated 10% of the collection before telling me I ran out of AI credits and I should upgrade my billing to support this. I don’t want to use AI. I just want my collection back, this is blocking my team.
Tried to use autofix, didn’t work. Above fixes also didn’t
I cannot make it work in any way… I have even tried installing Postman on a different machine and arch (Windows)… I did the following (which used to work):
- create a brand new Workspace
- create a collection
- create a request inside that collection
- export it ==> it generates a .json file with v2.1.0 schema, not the new V3 one
- place the file inside a git repo
- open that git repo folder in the Local View
- detects 1 collection (it says)
- Hit “Connect”
- Show the file tab with the "recognized“ collection (as show before)
- Go to the "Local Items“ tab
- NOTHING is displayed under COLLECTIONS section
- NO migration popup/assistant is triggered
- Completely useless
- Uninstalled v12
- Installed v11.86.1 on the same machine
- did the same above steps
- It worked
Hey @mcancelosi
Did you previous have a git repo connected to the Workspace before the update or is that something that you done after the move to v12?
I have the same issue after V12 update, i used to work in local, but now Postman dont recognize .json collections, and if y try Fix option, it try to reconvert to yaml the json file (it happend with collection and env)
Share the v11.86.1 link please, I dont faind in postman site
The workspace was previously connected to git. I will say that the same file works if i disconnect from git. That doesn’t make much sense.
https://dl.pstmn.io/download/11.86.1/osx_64
https://dl.pstmn.io/download/11.86.1/osx_arm64
https://dl.pstmn.io/download/11.86.1/win64
https://dl.pstmn.io/download/11.86.1/windows_arm64
https://dl.pstmn.io/download/11.86.1/linux_64
https://dl.pstmn.io/download/11.86.1/linux_arm64
1 Like
Hi all,
I just spoke with engineering. They have identified the issue and working on a fix. Thanks for flagging it here. I’ll update as soon as I know more and we can push an update.
7 Likes
Same issue here. Previous version were working normal in Local Mode. After upgrade, several collections need upgrade to v3 in JSON format: “Legacy v2 JSON file found. Convert to v3”.
Blocked at this point.
Hey @StivenSalazar
Do you have a Fix option to the right hand side of that view? Its hard to see as it’s not a full app image.