as the great new native IOS App does not (yet) support IPad’s I need to use Mattermost Classic there for now. Unfortunately I found a serious issue with it in private chats.
The app get’s into a state where messages written in Mattermost Classic are not transmitted to the server. This is intermittent, but can be triggered by writing some messages to the partner without waiting for his reply.
The messages which are typed in MM Classic are shown quite normally in MM Classic as if they have been successfully sent to the server. But they do not show up at the partner neither in the chat of the user which uses MM Classic if he opens the chat on a different device or in the web server.
If the MM Classic is completely closed (the app is ended by the task manager) and then reopened, the affected messages are also gone here.
Steps to reproduce
Open a private chat between two users, one user is using MM Classic on the IPad.
Type a message on MM Classic. The first one should appear in the parter’s chat as expected. Without an answer, type 1 or 2 more messages in MM classic. The messages are still shown in MM Classic, but they do not appear at the partner.
If MM Classic is completely closed and restarted, the affected messages are also gone (hence they are not transmitted to the server).
The server logs do not show any error messages.
All messages should be transferred to the server correctly.
Messages are shown in MM Classic as sent, but they are not.
Tested with two IPads (IPad Air 2 / IOS 10.3.2) and IPad 3 (IOS 9.3.5)
MM Server: 4.0.2 (Currently running Enterprise trial)
MM Classic App: IOS 3.10.1
Apart from this: Maybe it would be useful to have a “transmitted” confirmation from the server like seen in other messaging apps like IMessage, WhatsApp etc. so one can ensure the server got his message