Unhandled Exceptions and Inadequate Error Handling in ViewModels

[Leizpig]

Several ViewModel methods (e.g., ChatViewModel.sendContent, ChatViewModel.retryMessage) use require statements and only print stack traces in their coroutine exception handlers. This can cause the app to crash or fail silently without user feedback if an exception occurs.

Steps to Reproduce

• Trigger an exception in a ViewModel coroutine (e.g., by providing invalid input or causing a network failure).
• Observe that the exception is only printed and not handled gracefully.

Expected Behavior

• Exceptions should be caught and handled with user-friendly error messages or UI feedback, not just logged or printed.

Suggested Fix

• Implement robust error handling and user notifications in all ViewModel coroutine scopes.
• Consider using a shared exception handler with UI feedback mechanisms.