Mobile: Long error messages during sync causes all notebook to be hidden

[narFnarF]

On iOS, when an error occur during during sync, the error message is often incomprehensible and very long, which pushes all notebooks up and out of view.

Environment

Joplin version: 12.8.1 Platform: iOS 15.5

Steps to reproduce

1. Launch Joplin mobile on iOS
2. Sync in a way that will cause a long error message (ex: Sync with a Nextcloud instance that's under maintenance or with its storage space full)
3. Observe Joplin's side panel (the list of Notebooks) : the error message takes all the space

Describe what you expected to happen

Error message is displayed in a concise way.

Notes

This issue is problematic for a number of reasons. First, the error message hides the list of notebooks because it's too big. But then the error is also cropped at the bottom, so we can't see the full error message if we need to. And finally, in the majority of cases, the error message itself is unnecessary, since the only thing we care about is if the sync was successful or not.

For these reasons, I suggest that, when an error occur, Joplin would only display a warning icon ⚠️. This would make it clear that an error occurred and the sync wasn't successful. Tapping the ⚠️ icon would open a popup with the full error displayed, in a scrollable text box, so that we can scroll and be able to read the whole error message if needed.

Logfile

[github-actions[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[narFnarF]

It's hard for me to test again, but as far as I can tell, the issue still occurs.

[github-actions[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.