You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The app, over the past year has continued to degrade and become agonizingly slow over the course of a week or so of usage. I, and numerous other people at my organization, have been forced to delete/reinstall the app as often as every 2 days in order for it to continue working. The slowness exhibits itself when selecting a channel to respond to. It can take over 5 seconds for user action to be recognized and acted upon. Recently, the app has also started force closing when attempting to read a channel OR create a post.
@amyblais would be great if the team would take a look at this issue and the linked issue noted above. The original issue has been open over a year with no response and not even noted as a bug report by a label yet. This issue affects between 200 and 300 users at my org.
Summary
The app, over the past year has continued to degrade and become agonizingly slow over the course of a week or so of usage. I, and numerous other people at my organization, have been forced to delete/reinstall the app as often as every 2 days in order for it to continue working. The slowness exhibits itself when selecting a channel to respond to. It can take over 5 seconds for user action to be recognized and acted upon. Recently, the app has also started force closing when attempting to read a channel OR create a post.
Environment Information
Steps to reproduce
Use a mattermost server that has stats similar to the screenshot. Perform ANY action after using the app for a week.
Expected behavior
WAY faster responsiveness to user actions. NOT force closing itself.
Observed behavior (that appears unintentional)
No error messages ever. App becomes slow taking upwards of 5 seconds to respond to any input AND force closes itself.
Possible fixes
If you can, link to the line of code that might be responsible for the problem
The text was updated successfully, but these errors were encountered: