<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - iOS App Crashes with Invalid Template URL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124918#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - iOS App Crashes with Invalid Template URL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124918">bug 124918</a> from <a class="email" href="mailto:andreas.gruhler@adfinis-sygroup.ch" title="Andreas Gruhler <andreas.gruhler@adfinis-sygroup.ch>"> Andreas Gruhler</a> <pre>(In reply to Tor Lillqvist from <a href="show_bug.cgi?id=124918#c7">comment #7</a>) > After the above commits (which are also present in the branch from which the > iOS app is built for the customer), empty lines or invalid URLs in the file > no longer crash the app. > > About error messages, should they really be displayed to the user? The end > user can't do anything about it anyway. Would it be better to just NSLog > them, so that a support person can see them using whatever tool they use? On one hand, as long as an end user is able to modify this setting through the UI and choose another template URL in the iOS-Settings, it makes sense to also provide her the error message in case something goes wrong (maybe in a simplified form). On the other hand, if the template URL were a setting only accessible by an admin or super-user, I'd rather not show it to an end user. In any case, writing the errors to NSlog can be helfpul.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>