You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Send a message with a link to an inaccessible file (e.g. internal link, no share from C to A) from account C to account B
Open the link as account B
Expected behaviour
The link should be opened in the browser as the Files app can not open the file.
Actual behaviour
The Files app opens but crashes because the only available user A does not have access to the file.
Device brand and model
Pocophone F1
Android version
14
Nextcloud Talk app version
19.0.1
Nextcloud server version
No response
Talk version
No response
Custom Signaling server configured
None
Custom TURN server configured
None
Custom STUN server configured
None
Android logs
No response
Server log
No response
Additional information
This might very well be an issue in the Files app instead, as it should not crash but open the link in the browser once it realizes that the logged in account does not have access to it.
The text was updated successfully, but these errors were encountered:
Ok I was wrong, account B was also logged in at the Files app.
It only crashes when the active account is not B, if it is B it opens as expected.
So this might be an issue of the Files app entirely, although it could also be something in the communication between the Talk and Files apps.
Steps to reproduce
Expected behaviour
The link should be opened in the browser as the Files app can not open the file.
Actual behaviour
The Files app opens but crashes because the only available user A does not have access to the file.
Device brand and model
Pocophone F1
Android version
14
Nextcloud Talk app version
19.0.1
Nextcloud server version
No response
Talk version
No response
Custom Signaling server configured
None
Custom TURN server configured
None
Custom STUN server configured
None
Android logs
No response
Server log
No response
Additional information
This might very well be an issue in the Files app instead, as it should not crash but open the link in the browser once it realizes that the logged in account does not have access to it.
The text was updated successfully, but these errors were encountered: