nextcloud/talk-android

Default constructor must be used with fragments

parneet-guraya opened this issue · 0 comments

Steps to reproduce

Both FilterConversationFragment and DateTimePickerFragment have parameterized constructor which would lead to crashes on configuration changes as activity would look for default constructor to instantiate fragment.

FilterConversationFragment

document_6269276466760912910.mp4

DateTimePickerFragment

document_6269276466760912911.mp4

Expected behaviour

Should handle configuration changes.

Actual behaviour

Crashes the application as activity couldn't find default constructor.

Device brand and model

OnePlus 9RT

Android version

14

Nextcloud Talk app version

v 19.0.0 Alpha 01

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

Solution -->

  • Make the fragments use default constructor and instead use arguments to pass data.