That’s rather complicated and time-consuming, since this error message does not concerns debugging the app itself. Instead, it’s an information for end-users in their everyday workflow (comparable to “wrong password”).
A wrong password doesn’t violate a standard.
Therefore, I would (at least) extend the message of the IllegalArgumentException with the specific title of the respective task.
Thanks for the suggestion. I’ll have a look at that. I guess we would need another try/catch block for
IllegalArgumentException (which is not generated by DAVdroid/ical4android, see below) and wrap it into another exception. Wouldn’t the
UID be more useful?
SUMMARY is optional.
Btw.: why do you enforce this constraint? Is there anything more than “RFC 5545 told it”?
- In my opinion, it would be enough reason that RFC 5545 tells it.
- DAVdroid/ical4android doesn’t enforce this constraint. If you have a look on the stack trace, you can see that the exception comes from the content provider client, which receives it from the OpenTasks content provider. So, it would be better to ask the OpenTasks developer(s) about details.