Wrong token copied after application rename

[disconn3ct]

Can the issue be reproduced with the latest available release? (y/n) y Which one is the environment gotify server is running in?

• [x] Docker
• [ ] Linux machine
• [ ] Windows machine
  Docker startup command or config file here (please mask sensitive information)

  
  

Do you have an reverse proxy installed in front of gotify server? (Please select None if the problem can be reproduced without the presense of a reverse proxy)

• [ ] None
• [x] Nginx
• [ ] Apache
• [ ] Caddy
  Reverse proxy configuration (please mask sensitive information)

  
  

On which client do you experience problems? (Select as many as you can see)

• [x] WebUI
• [ ] gotify-cli
• [ ] Android Client
• [ ] 3rd-party API call (Please include your code)

What did you do? Rename an application (app1), then click the "copy token" on the same application without leaving the page.

What did you expect to see? Messages with that token are received on that application (app1).

What did you see instead? (Include screenshots, android logcat/request dumps if possible) The token was for a different app (app2). When opening the apps page again, the row holding app1 was now holding app2. It looks like the rename caused the tokens to be reordered without changing the visible names.

[jmattheis]

Cannot reproduce, could you give more detailed steps on how to reproduce this? repro.webm

[disconn3ct]

I tried a few times and could not get it to reproduce. It visually reorders them as soon as the new name is submitted and the tokens match the names.

I think there must have been something wedged that prevented the refresh. Maybe still a bug, but not a useful one :( Sorry for that.