starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 17:26:03 +03:00

[GH-ISSUE #5690] [bug]: Postman Collection v2.1 import succeeds, but clicking any request doesn’t load editor (Vue runtime-6: auth not an object #2211

New issue

Closed

opened 2026-03-16 23:35:05 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 23:35:05 +03:00

Owner

Originally created by @akramrana on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5690

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Web App

Browser

Firefox

Operating System

Windows

Bug Description

🧩 Summary

When a Postman Collection v2.1 is imported into https://hoppscotch.io, the import completes successfully and all folders/requests appear in the sidebar.
However, clicking any request does not load it into the editor.

The browser console shows a Vue runtime error indicating Hoppscotch is attempting to mutate an auth property on a stringified JSON, not an object.

🔁 Steps to Reproduce

Export a collection from Postman using Collection v2.1
Open https://hoppscotch.io/
Import the JSON collection
Import completes successfully and requests appear in the sidebar
Click on any request

✅ Expected Behavior

Clicking a request should load it into the editor (method, URL, headers, body, auth, etc.)

❌ Actual Behavior

Request does not load in the editor
Sidebar selection changes, but editor remains empty
Vue runtime error appears in browser console

🧪 Console Error (Firefox)

[Vue warn]: Error in https://vuejs.org/error-reference/#runtime-6:
"TypeError: can't assign to property 'auth' on
'{"auth":{"authType":"inherit","authActive":true},
"headers":[],
"variables":[{"key":"auth","initialValue":"REDACTED","currentValue":"","secret":false}],
"description":null}': not an object"

(found in <Anonymous>)
    onSelectRequest TeamCollections.vue:378
    Request.vue:363


### Deployment Type

Hoppscotch Cloud

### Version

_No response_

Originally created by @akramrana on GitHub (Dec 12, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5690 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Firefox ### Operating System Windows ### Bug Description ### 🧩 Summary When a **Postman Collection v2.1** is imported into **https://hoppscotch.io**, the import completes successfully and all folders/requests appear in the sidebar. However, **clicking any request does not load it into the editor**. The browser console shows a Vue runtime error indicating Hoppscotch is attempting to mutate an `auth` property on a **stringified JSON**, not an object. --- ### 🔁 Steps to Reproduce - Export a collection from **Postman** using **Collection v2.1** - Open **https://hoppscotch.io/** - Import the JSON collection - Import completes successfully and requests appear in the sidebar - Click on **any request** --- ### ✅ Expected Behavior - Clicking a request should load it into the editor (method, URL, headers, body, auth, etc.) --- ### ❌ Actual Behavior - Request does not load in the editor - Sidebar selection changes, but editor remains empty - Vue runtime error appears in browser console --- ### 🧪 Console Error (Firefox) ```text [Vue warn]: Error in https://vuejs.org/error-reference/#runtime-6: "TypeError: can't assign to property 'auth' on '{"auth":{"authType":"inherit","authActive":true}, "headers":[], "variables":[{"key":"auth","initialValue":"REDACTED","currentValue":"","secret":false}], "description":null}': not an object" (found in <Anonymous>) onSelectRequest TeamCollections.vue:378 Request.vue:363 ### Deployment Type Hoppscotch Cloud ### Version _No response_

kerem

2026-03-16 23:35:05 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-16 23:35:21 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Dec 12, 2025):

Hi, apologies for the inconvenience. We've identified the root cause stemming from the BE implementation on the cloud offering, and a patch is being evaluated. Please track the further progress in #5670.

@jamesgeorge007 commented on GitHub (Dec 12, 2025): Hi, apologies for the inconvenience. We've identified the root cause stemming from the BE implementation on the cloud offering, and a patch is being evaluated. Please track the further progress in #5670.

kerem commented

2026-03-16 23:35:26 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Dec 12, 2025):

The fix is now live. Please let us know if the issue persists.

@jamesgeorge007 commented on GitHub (Dec 12, 2025): The fix is now live. Please let us know if the issue persists.

kerem commented

2026-03-16 23:35:31 +03:00

Author

Owner

@akramrana commented on GitHub (Dec 13, 2025):

The fix is now live. Please let us know if the issue persists.

Thanks it is working now.

@akramrana commented on GitHub (Dec 13, 2025): > The fix is now live. Please let us know if the issue persists. Thanks it is working now.