Updating to 3.3.0 RC1 causes native apps to stop working.
Existing native apps to work after update
I'm seeing lots of these entries in the mattermost.log
file:
/error:CheckBrowserCompatability code=500 rid=8oa8pn43p3dwbp3k4cfo5qtywr uid= ip=%%%%, %%%% Your current browser is not supported, please upgrade to one of the following browsers: Google Chrome 21 or higher, Internet Explorer 11 or higher, FireFox 14 or higher, Safari 9 or higher [details: ]
There might be 2 issues here:
Android screenshot, to confirm version:
Safari 10 screenshot (for macOS app):
Confirmed with @cgsmith that reinstalling the Android native application made it work again.
It is working fine for me now. I'd like to request a feature to handle the error so at least it is not a white screen.
Thank you for the report @johnjamesjacoby, and for your feedback @cgsmith!
I've created a ticket for us to track the issue in Jira: https://mattermost.atlassian.net/browse/PLT-3839
Our desktop community has been working on re-validating cache upon load to prevent this issue in the future. If you'd like, you can download the test version for Mac to see if the issue reproduces with the changes.
@jasonblais can you also note this down for the developers? It seems like the following might indicate a high priority on the issue.
For Android and Linux desktop (Ubuntu 16.04.1 LTS xenial - MatterMost Desktop 1.2.1) the app is pretty unresponsive. I cleared the cache and reloaded on the desktop application. Reloading the page is the only way to get new messages to come through from team members.
On the phone, I get push notifications with direct messages, but I do not see them come through on the phone. I have to reload the page in order to see it as well. v3.2 worked much better and we might move back to it if possible.
Seems like the cache issues or other issues are very broken in this release.
Anything I can do for testing or to help troubleshooting on your end?
@jasonblais perhaps this is related to socket rules? Here are console:
This could be a red herring as well :/
In the process of diff'ing the config.json
I omitted/removed the SiteURL
setting. I'm not sure if that would cause all of this, but my guess is Mattermost not knowing what it's own URL is will have all sorts of strange consequences.
Also probably unhelpful, after updating to RC2, I think everything else is working OK after a cache purge & refresh.
I just saw #3764 and now I don't know what is real life anymore. ¯_(ツ)_/¯
This issue may be related, so I encourage you to wait a couple of days until RC3 is cut and then you can test it back and post your findings :)
Thanks again for the report @johnjamesjacoby and @cgsmith !
We just cut RC3 where this issue should be fixed.
Please let us know if the issue still occurs?
Thanks @jasonblais. I'll try RC3 and report back my findings either way.
Quick update @johnjamesjacoby , we're about to cut RC5, which should fix the problem. I'll give an update once it's been done.
Thanks again for the report!
RC5 has been cut -- feel free to let us know if you notice anything.
A huge thanks to you @johnjamesjacoby and @cgsmith for reporting the issue!
Thanks @jasonblais. No (noticeable for us) issues with either 3 or 4. I'll report back if 5 gives us any grief.
This is what open source is for! Thanks for making a great product!
RC5 humming along A-OK.
Great to hear!
Thanks @johnjamesjacoby and @cgsmith for making a difference in v3.3! Love it
Happy to, @jasonblais! We're just getting started. 💜