Help testing 2.49+ bugfix releases

and now: here is Delta Chat 2.49.0 - choose your flavour and mind your backups:

this version contains mainly bugfixed of the big 2.48 release.

see the changelogs at https://get.delta.chat#changelogs for details - and we again happily read your feeback here. thanks all for testing and reporting tirelessly :folded_hands:

The call reception screen does not appear on a blocked screen, not on Xiaomi, not on Huawei, all permissions are given

deltachat-log-20260415-131401.txt (3.4 KB)

deltachat-log-20260415-131917.txt (61.9 KB)




Multiple accounts running simultaneously on Windows and Android.
When I receive an incoming call, I immediately receive a missed call notification.
Devices: Windows 10, Samsung (SM-S908E).
Incoming calls work fine on two other devices with different accounts on one Samsung device (SM-908B).

Flashed mobile with GrapheneOS and still have same problem.

On answering voice call from standby call it just drops.

Pixel 7

thanks for reporting! i filed an issue for that at incoming call results in missed call notification · Issue #4362 · deltachat/deltachat-android · GitHub

Random error I’m getting is with recording the audios. Some of them do fine, some can’t be played by both parties. It shows as zero length voice message.

I didn’t have such behavior on previous versions. I believe this started around 2.46-47, but I might be wrong.

I managed to record this behavior:

Also I have two imported relays, they are active on pc and phone two.

On PC I often get two simultaneous sent messages, one which is read and one not, doesn’t matter if it’s text or audio:

Have you been experiencing that on previous versions of Delta Chat?
Have you tried putting your Android device in airplane mode and then receiving a call?

В версиях до марта месяца входящие звонки работали нормально.

I’ve received this message in the device message chat:

Failed to receive a message: Failed to load webxdc instance that we just checked exists: Message Msg#9024 does not exist. Core version v2.49.0. Please report this bug

Not sure how can I get more information to debug it.

Edit: I’m using deltachat and arcanechat on my mobile, deltachat on desktop and this message showed on the laptop after did a long sync since I don’t use it very often.

hi, when reporting problems it is always useful to state all the versions of delta chat of every device involved, could you please provide that info? thanks in advance

Hello, in my case it’s 2.49.0.

That’s why I wrote into this topic.

Привет нашёл серьёзный баг в delta chat 2.49 не могу ответить на входящий звонок, нажимаю ответить и ничего не происходит, не реагирует на кнопку. Могу приложить видео если нужно. android 13.

Eng

Hi, I found a serious bug in delta chat 2.49 I can’t answer an incoming call, I click answer and nothing happens, it doesn’t respond to the button. I can attach a video if necessary. android 13.

баг номер 2 не могу позванивать с Android на Windows вызов не проходит.

Eng

Bug number 2 can’t call from Android to Windows, the call doesn’t go through.

Сегодня общался с собеседником по Delta chat у него Iphone у меня Android На Android новый интерфейс звонков и он говорит что меня тихо слышно через новый интерфейс Может разработчики обратят на это внимание, На старом интерфейсе звонков который используется в Windows версии с громкостью всё нормально.

This might be due to the Speaker / Earpiece distinction (4th button in the new Android UI). Try to switch to Speaker.

Я собеседника хорошо слышу, у меня (Android) А вот он меня слышит тихо у него Iphone (У него динамик включён.)

That’s so annoying, how can I update to 2.50 if this has been fixed?

Phone/Video calls initially worked - although when connected to a VPN it would freeze every few seconds briefly. Turning the VPN off fixed this.

However, after adding extra relays, the calls are now not connecting, as soon as the person answers the call, it fails. Both ends of this issue were tested on Fairphones, running e/os on Delta Chat 2.49.0 downloaded through FDroid.

Could this be due to relay servers not correctly configuring the “TURN” server?

Sounds like a problem with the VPN being slowish.

How exactly does this happen? They press the button and then immediately the call ends (and goes to the “main screen” on both ends?

Also do you mind sharing the list of relays, possibly privately?

Sure, I can DM you the relays on delta chat.
(I’ve created a new profile for debugging and to not dox my personal profile)

I will experiment with the calls again later when my friend is online to document the issue more precisely and I will update you.

OK, the problem likely was that indeed one of the relays’ TURN server is not functional, and that was the one used for the call. I suspect though that what we actually want is to Calls: use all relays' TURN servers, not just one.