Invalid TimeZoneName error at launch of direct message or channel

[rebeccapetro]

Summary

App not allowing message viewing or posting since last update

Environment Information

• Device Name: galaxy s23
• OS Version: 14
• Mattermost App Version: 2.23.0
• Mattermost Server Version:9.11.4

Steps to reproduce

How can we reproduce the issue (what version are you using?) Open app on android, go to direct message or channel to view messages = Error

Expected behavior

I get push notifications fine but cannot post or view anything within the app without crash

Observed behavior (that appears unintentional)

See screenshots

[amyblais]

Opened https://mattermost.atlassian.net/browse/MM-62298.

[stmangm]

Set the time zone in MM to auto, and check the time to match your setting of 12 or 24 hours

[sanyocc]

Set the time zone in MM to auto, and check the time to match your setting of 12 or 24 hours

BS. I had default settings with a TZ in auto with matching 24hr setting, though the latest update broke MM app as everyone else I know in my org.

For us, workaround is setting your phone or MM app manually to another timezone.

[custardpy]

Same issue here. This exact error occurs both on my Android and iPhone devices. Colleаgues confirm the same behavior.
The error has been introduced with the latest app update? Impossible to use the app since.
Mattermost server version: 10.2.0
Current Android app version: 2.23.1
Current iOS app version: 2.23.1

[coltoneshaw]

Workaround identified as:

Secondary workaround tested:

1. Set system time to new timezone
2. Set system time to 24h clock
3. Set mattermost to new timezone
4. Set Mattermost to 24h clock

[henk23]

The workaround does not work for me. Setting the Android system to a new timezone does not help.

Setting Mattermost app to new timezone is not even possible, it always reverts to "auto" immediately.
Setting system/Mattermost to 12/24h clock does nothing.

[oli-ver]

In my case all users are affected. From the jira issue's comments I understand that setting our phones and the mattermost server to one of the non-crashing timezones like UTC is the only workaround right now. I wonder why this GitHub ticket was closed. Will the bug be tracked from the linked Jira side? I don't think everyone can switch their phones to UTC for the sake of the mattermost app

[phaus]

The App was working before without any issue…
I cannot really set my iPhone's timezone to UTC. So my workaround is to use the browser only…
Which drasticly reduces the user experience…
Is there an explanation somewhere why this is happening with the most recent version?

[enahum]

Can you please post the affected timezones, maybe that will help to check it out

[oli-ver]

In the Jira issue @lindalumitchell posted the unaffected and affected timezones she tested:

"Time zones I tested that DO crash: CET, EET, EST, GMT, HST, MET, MST, MST7MDT, PST8PDT, ROC, WET
Time zones I tested that do NOT crash (a small selection from the list that seemed potentially out of format): Cuba, Eire, Etc/UTC, GB, GMT+0, GMT-0, GMT0, Greenwich, NZ, PRC, ROK, UCT, UTC, W-SU"

Our server is in Europe/Berlin which is the timezone of all users as well. One user who is traveling is in UTC+5:30 and is affected as well.

[oli-ver]

In our case upgrading the server from 9.2.0 to 9.11.6 fixed the issue.

[infra-monkey]

Same issue.
server version 9.11.6
mobile version 2.23
server TZ = UTC
user traveling to Argentina is affected with the issue. On mobile ios I can see 12 timezones available for argentina while on desktop there is only Buenos Aires for argentina

[enahum]

@larkox can you take a look at this?

[ThiefMaster]

One of my users has the same problem:

The timezone is set to adjust automatically. The time zone that both, the Phone and the iPad are currently using is „Rio Gallegos“
On the iPad Mattermost crashes right away. On the phone it only crashes once I click a channel or a chat.

Server version is 9.11.6

[zhix]

Server Version: 9.1.1 (Build 9.1.1)
App Version: 2.23.1 (Build 6000587)
App Platform: android
Device Model: Xiaomi 11T Pro

We are facing this issue as well.

Another user is using iPhone

[kenricnelson]

I'm noticing particular difficulties with UTC. On the Apple iOS 17.6.1, UTC is an option but it reads GMT once entered. Interestingly neither GMT nor Greenwich show up in the Apple search for timezones. When I set the iOS timezone to New York or Los Angeles, the Mattermost app v2.23.1 opens properly. Once I set it back to UTC the problem reappears.

[larkox]

We will be releasing a dot release (2.24.1) with this fix soon.

[kenricnelson]

Okay, thanks for the update.

…

On Fri, Jan 17, 2025 at 08:45 Daniel Espino García ***@***.***> wrote: We will be releasing a dot release (2.24.1) with this fix soon. — Reply to this email directly, view it on GitHub <#8423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJD5LBCTPUA6CKP534Q6M6L2LC7K7AVCNFSM6AAAAABTY6EZOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJXG4YTOMRZGM> . You are receiving this because you commented.Message ID: ***@***.***>

[infra-monkey]

I have confirmation from my user in argentina that the issue is fixed with v2.24.1

[kenricnelson]

Thanks I’ll try it out

…

On Sun, Jan 19, 2025 at 16:34 Antoine Gatineau ***@***.***> wrote: I have confirmation from my user in argentina that the issue is fixed with v2.24.1 — Reply to this email directly, view it on GitHub <#8423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJD5LBBLLNOB7Y7POFGT4632LPHYPAVCNFSM6AAAAABTY6EZOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQHEZTGOJTHE> . You are receiving this because you commented.Message ID: ***@***.***>