Lost all my requests and collections after the new update (2022.7.0)

[tkurskiev]

I'm very angry and I delete this app. This is bullshit, guys.

Yeah, I was able to find them in "C:\Users\User_name\AppData\Roaming\Insomnia\insomnia.Request.db", but this is very unpleasant experience.

[timoheutsrs]

How did you managed to import the data again? I keep getting errors when opening that file

[tkurskiev]

I opened it in Notepad++, analysed and copied what I need by hand into Postman

[inafil76]

After the 2022.7.0 update, I keep getting errors when I open my Collections. They are now labeled as Documents and the error says that they don't follow the correct format for a document.

Tried exporting and importing again but it seems that importing has issues also.
This really takes me back, I had a LOT of work in those collections...

[thayaneBomfims]

Concordo completamente. Perdi todas as requisições com essa atualização ridícula. Todos me dizem para utilizar o Postman e eu sempre relutei, mas estão certos. Esse app é um lixo mesmo, vivo tendo problemas

[aidarchikable]

I lost all my collections and environments because of the last update.
And I'm very disappointed because I used Insomnia as a replacement for Postman, but now Insomnia has become Postman.

[josejesusrl]

La verdad no me gustó la actualización, me gustaría regresar a una versión anterior o buscar un nuevo cliente rest

[TheKayThatWasOrange]

It's funny how they keep doing this over and over and keep getting angry at users "spamming" their issues with complaints about how completely irresponsible they are.

[subnetmarco]

Since a very long time Insomnia has had weird edge cases to implement flawless migrations across different types of data structures across versions. We are taking action and have fully allocated resources to finally build reliable migrations and try to eliminate these edge cases, which were caused by very old code.

These migrations happen on the file system, and needed more resourcing to properly handle all sort of edge cases that happen when interacting with the underlying I/O, failures and so on.

As such in v8.3 we shipped many of those improvements already, and in v8.4 we are shipping another large set of improvements with better error handling in those circumstances.

In the meantime, I offer one of our Insomnia engineers to hop on a Zoom call to debug and look at the migration problems you may experience. We are literally collecting all the edge cases as we speak via many of these calls.

@TheKayThatWasOrange Complaining about legitimate issues is not spamming. But actual spamming is..spamming, and also in violation of the terms of service of GitHub.

[TheKayThatWasOrange]

Maybe you can go throw another tantrum on HN about it.

[subnetmarco]

Closing this discussion since we have implemented several improvements and we are not seeing this issue popping up anymore. I will re-open it if the issue persists.