Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App becomes amazingly slow and often force closes #7872

Open
giffmann opened this issue Mar 18, 2024 · 2 comments
Open

App becomes amazingly slow and often force closes #7872

giffmann opened this issue Mar 18, 2024 · 2 comments
Labels
Bug Report/Open Bug report/issue

Comments

@giffmann
Copy link

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

  • Device Name: iPhone 13
  • OS Version: iOS 17.4
  • Mattermost App Version: 2.14.0/2.13.0/2.12.2/2.12.1/2.12.0
  • Mattermost Server Version: 8.1.7

Steps to reproduce

Use a mattermost server that has stats similar to the screenshot. Perform ANY action after using the app for a week.
image

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

@giffmann
Copy link
Author

Second time reporting this issue as per the iOS app store. First issue, reported nearly a year ago is linked below.

#7322

@giffmann
Copy link
Author

@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.

@amyblais amyblais added the Bug Report/Open Bug report/issue label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report/Open Bug report/issue
Projects
None yet
Development

No branches or pull requests

2 participants