talk-android
talk-android copied to clipboard
nextcloud
Talk 14.2.0 rc2 loads blank.
Steps to reproduce
- Open talk
- No list of conversations Cant change server or settings. UI is blank
Expected behaviour
Open talk and see a list of conversations.
Actual behaviour
Talk opens blank. And if i choose to create a conversation it crashes
Device brand and model
Oneplus 9 pro
Android version
12
Nextcloud Talk app version
14.2.0 rc1
Nextcloud server version
24.0.4
Talk version
14.0,4
Custom Signaling server configured
Yes (specify version in Additional Information)
Custom TURN server configured
Yes
Custom STUN server configured
Yes
Android logs
No response
Server log
No response
Additional information
Connected to three different servers.
Two Nextcloud 24.0.4 with talk 14.0.4 with an external hpb and turn server. Both are pretty identical. One is the nextcloud.com instance.
- can you reinstall the app and see if this happens for one specific server or if it happens only when you use both?
My own two instances work. I cant add the nextcloud.com one since 2fa is broken for guest users at the moment. I'll try another phone and see if that also breaks.
i just tried out nextcloud.com with another guest account. I get the error "unsupported server". So this might be related. i will have a closer look!
i just tried out nextcloud.com with another guest account. I get the error "unsupported server". So this might be related. i will have a closer look!
can't reproduce this anymore :confused:
@small1 just to sum up here what was discussed in chat: this happens because you try to use webauthn?
I reproduced this on one more oneplus. It happens when its upgraded from another version to 4.2.0 rc2 but once storage is wiped and accounts are added back it works as it should again.
It has nothing tod o with 2fa. The 2fa stuff was noticed when i readded the accounts that ive had for quite some time and was setup with older 2fa app. so webauthn is a completly other type of bug
So @timkrueger and I tested various paths, most important,
- 14.0->14.2
- 13.0->14.2
without any issues, so we can't reproduce this issue. The empty screen comes up if the client can't load any talk data since the Android app currently doesn't have any offline capabilities so all data gets fetched from server or if you would face some database issues where we can't retrieve the user infos or cookies&/session. The big structural change with 14.1 and 14.2 was the complete replacement of the db access layer as well as the cipher upgrade for the db encryption
An idea would be to show
- log error in log file
- show an user error: login failed, please click here to re-authenticate
I think i went from 14.2.0rc1 to rc2 or a version before that to 14.2.0 rc2 Im in the beta channel and i tend to make sure i have updated all apps every week. And it might have been something that has been lurking since an earlier version that that that just exploded in the rc2 version
So this might not be an issue that will occur later on.
In my case i tested access from my computer and other phone in paralell and broth from wifi and mobile network. Just to exclude a non reachable server :)
Steps to reproduce
- Open talk
- No list of conversations Cant change server or settings. UI is blank
Expected behaviour
Open talk and see a list of conversations.
Actual behaviour
Talk opens blank. And if i choose to create a conversation it crashes
Device brand and model
Oneplus 9 pro
Android version
12
Nextcloud Talk app version
14.2.0 rc1
Nextcloud server version
24.0.4
Talk version
14.0,4
Custom Signaling server configured
Yes (specify version in Additional Information)
Custom TURN server configured
Yes
Custom STUN server configured
Yes
Android logs
No response
Server log
No response
Additional information
Connected to three different servers.
Two Nextcloud 24.0.4 with talk 14.0.4 with an external hpb and turn server. Both are pretty identical. One is the nextcloud.com instance.
I have set up a Nextcloud server, and some of our Nextcloud Talk users on smartphone are experiencing the same issue since the update of Nextcloud toward 24.0.4. They cannot load conversations, or access them, unless they wait for a long time enough.
From users reports, this seems to happen both under iOS for IPhone users, and Android. All users are not impacted with the same severity : Maybe those who have a longer history of use have to wait for a longer time when opening the app ?
Displaying an info dialog would be nice of course, but more important: what should we recommend the users to do in such case ? Should we ask them to reinstall the Nextcloud Talk app ?
Thanks a lot for all the information shared here and the incredible job you're doing !
Something similar to @YoannPa happening here... but on Nextcloud Server v23.0.8.
The terminals in this case are ALL android with nextcloud-talk v1.4.2, and all users are not impacted with the same severity, some of them have this problem on shared conversations between them... were another in the same conversation don't have... It depends on the "terminal". It happens different on some terminals being them connected to the same Wifi, so i discard the connection. It's very strange.
My phone (xiaomi mi 9, android 12, nextcloud talk v15.0.0-RC1) on this scenario, normally works ok.
When nextcloud-talk v15.0.0 got released on google play i will report it about the other terminals.
Device brand and model
Different Android Terminals
Android version
12
Nextcloud Talk app version
v14.2.0
Nextcloud server version
23.0.8
Talk version
13.0.8
Custom Signaling server configured
No response
Custom TURN server configured
Yes
Custom STUN server configured
Yes
Android logs
No response
Server log
No response
Additional information
No response
It seems to be fixed.
I can't reproduce it anymore.
On January 11, 2023 10:02:55 Marcel Hibbe @.***> wrote:
is this still an issue or is it fixed with the latest version? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Most users not complaining anymore on my side. So... no idea but it sounds positive I guess.