![]() ![]() Adding an email address to an existing contact That way we can fix them before they make it into a stable release. We’re very grateful to our beta testers for finding and reporting bugs like this one. That way we are likely to catch bugs related to such email addresses before they make it into a beta release. We added a message with an email address whose local part exceeds the length limit to our test account.But this will no longer lead to failing to load the entire message list. This may lead to the app not being able to fetch a contact name for an spec-violating email address. Ignore errors with the email address when trying to fetch the system contact belonging to that email address.However, we still want to be strict when it comes to the email addresses we accept, e.g. The world is full of email addresses that violate the specification but work mostly fine in practice. Ignore most errors when parsing email addresses from messages that the user has received.To fix this bug and limit the impact of similar problems in the future, we made the following changes: When an error occurs during this step, an empty message list is shown to the user. This lookup is performed when loading the message list of a folder from the local database. However, it turned out the new email address parser was used when getting the contact name belonging to an email address. We deliberately kept this new implementation out of the code responsible for parsing emails after download and the code for displaying messages. At first it was a bit surprising that this would lead to messages in a folder not being shown. The error was thrown by a newly added email address parser that is stricter than what we used before. Using the provided debug log (❤️) we were able to track this down to a message containing an invalid email address, specifically one whose local part (the text before the symbol) exceeds the limit of 64 characters. Folder appears to be emptyĪ user reported that some of their folders appear to be empty in K-9 Mail. Here’s a writeup of just three of the bugs we fixed in June. Fixing bugs is a large and important part of the job. Having an app with a large user base means we can’t spend all of our time working on new features. Hopefully there will be new screenshots to share in July’s progress report. ![]() We mostly worked on the internal plumbing that is important to get right, but not necessarily great material for a blog post. However, for June there’s no exciting news to share. Most of our time went into working on this. The roadmap item we’re currently working on is Improve Account Setup. If you need a refresher on what happened the previous month, read the May 2023 Progress Report. But a late report is better than no report □ Apparently our July has been so busy that we didn’t find the time to write up the progress report for June. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |