Golden Edition License Key: Licence key already in use

[Ogalesha]

I have checked the following:

• [X] I use the newest version of bruno.
• [X] I've searched existing issues and found nothing related to my issue.

Describe the bug

Hello,

I'm facing a problem on Bruno Golden Edition. I've two licence keys I used on two PC. (Pc 1 and Pc 2).

I formatted Pc 1, changing OS from Windows to Ubuntu and reinstalled Bruno. Once I tried to activate the first licence, I'm getting this error message "Licence key already in use".

Isn't there a way to reset the licence associations, so I can use the same licences on the same machines every time I've to set them from the beggining?

.bru file to reproduce the bug

No response

Screenshots/Live demo link

[discypher]

I have a similar issue, though I did not wipe my OS or uninstall Bruno. Suddenly my install was unregistered and now that same license key says it is already in use.

[bohemima]

Same error here but I haven't reinstalled my Mac, license was suddenly not recognised anymore and trying to enter the license key again fails with the above mentioned error.. :(

[jwetzell]

This was brought up in the discord by a user and the response was to contact [email protected] this issue should probably stay open if there is an actual bug with how bruno handles license during an upgrade/etc as that seems like a big annoyance to have to go through this process or not upgrade.

[melroy89]

It should be possible to "release" the key yourself in Bruno, before you format your disks/reinstall the OS (whether it be Linux or Windows, etc). Allowing you to re-activate the existing key on the same system. Without the need for support.

At License -> there is a "Deactivate" button. I hope this will release the key??

Somebody tried to back-up the license.json file in ~/.config/bruno or am I saying something that is forbidden now?

[gsabater]

@melroy89 yeah, i tried to backup license.json accross machines but its not working. That file contains a jwt, and according to jwt.io it has this content

{
  "email": "xxx",
  "deviceId": "xxx",
  "licenseKey": "xxx",
  "userId": "xxx",
  "licenseId": "xxx",
  "iat": 1711044642
}

I assume that deviceId does not match after a hardware update (either a format or even a component change), and this is what breaks the license