The information provided in the license management that's outsourced to lemon squeezy is abysmal. The lack of differentiation between which activation is which with mulitple devices on the same OS is bad enough. When the same browser is used (or a browser App has to be used b/c the Mac App only runs on new machines), there's no way to id which key is which. Please come up with a method to retain these keys in the PWA or have a method to sign in that binds the user account to the keys. Each time the web-based version is closed & reopned, or a browser update is released, the keys have to be deleted, added back into the brower app, then api keys for each model need to be added. The initial step of choosing which device to dactivate is bad enough, but to have to do that each time the app is used is ridiculous. This seems to be related to the browser version, so if it is updated, the activation fails the next time due to the new browser version, the activation on the previous version has to be deleted, then a new one has to be added - then all of the api keys for each model.

Please authenticate to join the conversation.
Closed
Feature Request
Account Management
About 2 years ago
Get notified by email when there are changes.
Closed
Feature Request
Account Management
About 2 years ago
Get notified by email when there are changes.