I’m just making this note here publicly, since I was first going to pose this as a question, but then managed to solve it by myself:
For background, I recently switched my Mattermost from a tar archive installation to installing it from the package repository, and simultaneously switched it from using a MySQL database to using PostgreSQL, all in one fell swoop by exporting the old content, doing a fresh install, and then importing. This appears to have mostly worked, with just user profile images having been lost, and passwords requiring a reset, both of which (I’ve gleaned from various places) were to be expected.
However, all bot accounts also seem to have been converted into normal user accounts somewhere during this process. So far the only issue I’ve discovered resulting from this is this entry getting logged repeatedly:
Failed to get system bot caller="app/post.go:2205" component=post_reminders error="SqlBotStore.Get: Bot does not exist., resource "Bot" not found, id: <my system bot's id>"
I solved this by running
sudo -u mattermost mmctl user convert --bot "<bot id>" # replace <bot id> with your real system bot account id
Since that seems to have gone well (the error messages stopped), I went ahead and converted the rest of the bot accounts back to true bots likewise.
For anyone else stumbling across this thread when googling for this annoying problem: the issue here is that using special characters in your password on the DataSource line is broken: Can’t use special character in password in the DataSource property · Issue #1541 · mattermost/mattermost · GitHub
As stupid as that is, the easiest way to work around it is to set a password consisting of just alphanumeric characters. You shouldn’t have much use for it outside this anyway, so as not to make it ridiculously insecure.
@amyblais Alright, I finally managed to get through the signup. Here’s my suggestion, although it’s in moderation for now, so the link probably won’t work until it’s approved.
A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).
Hi @amyblais,
I could post this on the feature idea forum, but I can’t figure out how the signup on the site works. When I click on ”Create an account”, I get a prompt to verify my email address, and having done that, a page saying ”Go back to Production to finish logging in”. I don’t know what ”Production” is, and at no point was there any actual way to set up a password, so I can’t log in.
Summary
A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).
Environment Information
- Device Name: Samsung Galaxy A9
- OS Version: Android 10
- Mattermost App Version: 2.11.0
- Mattermost Server Version: 9.3.0
Steps to reproduce
- Receive a message notification on the Android app.
- Pull down the notifications.
- Expand the received notification.
Expected behavior
Have a ”Mark read” option underneath the expanded notification.
Observed behavior
No ”Mark read” option, only ”Reply”.
Summary
As of this writing, push proxy v5.25.0 was released 5 days ago, but the published assets on Github only include the source code.
Steps to reproduce
As per documentation,
wget https://github.com/mattermost/mattermost-push-proxy/releases/download/v5.25.0/mattermost-push-proxy.tar.gz
Expected behavior
Receive mattermost-push-proxy.tar.gz
Observed behavior (that appears unintentional)
404 Not Found
I have the same issue. I’m doing this in a Linux container (Ubuntu 20.04 inside Ubuntu 20.04), but like matthaios-easy-bi, I’m using npm run build:android to build (as per documentation). This has worked up until 2.0, but with 2.1 it always fails due to non-existent org.webrtc. Manually running npm install prior to npm run build:android makes no difference, nor does node node_modules/react-native-webrtc/tools/downloadWebRTC.js (although it does seemingly download the package successfully).
Here’s excerpts from the build output.
It’s not Mac-only either, I have the same issue trying to compile v2.1.0 on my Linux PC.
V2.0 had issues too, but FTBFS wasn’t one of them.
Hi @hmhealey,
Yes, it’s mainly about expectation. For an actual use case, I noticed this when mentioning an IRC channel name, which became a long, distracting and useless hashtag link, exacerbated by agglutination and multi-word hyphenation typical in Finnish, (e.g. #channelname-irc-kanavalla). I tried to make it less distracting by editing in a preceding backslash, only to discover that it didn’t work here.