[GH-ISSUE #4285] Save Button Fails to Save Newly Generated Token in Teams Workplace #1559

New issue

Open

opened 2026-03-16 20:50:22 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 20:50:22 +03:00

Owner

Originally created by @habboubah on GitHub (Aug 22, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4285

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When generating a new token in the Teams workplace, the save button does not appear to save the new token. Instead, it retains the old token generated before the new one.

Steps to reproduce

Open Hoppscotch in the Teams workplace.
Open the Properties of a Collection.
Go to the Authorization Tab.
Choose the Grant type as Authentication Code, and check the Use PKCE option and fill the other options.
Click the "Generate Token" button.
Click the "Save" button.
Open the Properties of the same collection again.
Observe that the old token is still displayed, not the newly generated one.

Environment

Production

Version

Cloud

Originally created by @habboubah on GitHub (Aug 22, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4285 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When generating a new token in the Teams workplace, the save button does not appear to save the new token. Instead, it retains the old token generated before the new one. ### Steps to reproduce 1. Open Hoppscotch in the Teams workplace. 2. Open the Properties of a Collection. 3. Go to the Authorization Tab. 4. Choose the Grant type as Authentication Code, and check the Use PKCE option and fill the other options. 5. Click the "Generate Token" button. 6. Click the "Save" button. 7. Open the Properties of the same collection again. 8. Observe that the old token is still displayed, not the newly generated one. ### Environment Production ### Version Cloud