Tag Archives: Bug

About bugs we found and fixed.

What’s in our latest release

Bug Fixes, Kerika, , , ,

A ton of bug fixes, most of them so obscure that no end-users ever spotted them, but since we track our error codes seriously we make sure we fix stuff that no one even knew fixing.  Some of the bug fixes are truly obscure, here’s a few from our latest version that’s easier to explain:

  • There were some problems related to how our iOS app was updating that were a result of Apple deciding not to support Progressive Web Apps anymore.  (Thanks for nothing, Apple.)
  • When a person renamed a file attached to a task or board, the file was appearing as having unread updates (orange highlight) to the user who made the change.
  • For our Kerika+Microsoft users, we needed to make sure the correct OneDrive icons were appearing where files were attached to tasks and boards.
  • Also for our Kerika+Microsoft users: OneDrive files are better support for users of our Whiteboards feature.
  • When a text field could potentially be auto-filled using the browser’s saved values, if a user selected a saved value it wasn’t displaying properly.  (Thanks to a breaking change in one of Chrome’s many, many updates — seriously, why are they releasing new versions every week?)
  • Dates shown for non-English users will now appear in the locally selected languages.
  • If a user opened a task on the mobile apps that had been found by doing a search, editing the task’s title was showing HTML characters.
  • Handling situations better where two people were making changes to the same task at the same time: users are warned if someone else has made changes that would get overwritten if they saved their own changes.
  • Improvements in the new user experience: this is, frankly speaking, a never-ending quest for us!
  • Fixed a situation where a new user who didn’t complete their signup returned later to Kerika: the language selection that’s the first thing that a new user does wasn’t working properly.
  • We made it easier for people to stop getting their 6AM task summary emails; we really should have done this a long time ago.
  • Fixed a long-existing bug that finally surfaced that omitted some tasks from the 6AM emails.

 

Fixed: issue with showing thumbnails of pictures

Kerika,

With our most recent update (which was yesterday), we have fixed a problem with thumbnails of attached images not showing correctly. (Not always, but sometimes.)

Here’s what the problem used to look like:

Example of a missing update

As you can see, this card has two images attached. The first one doesn’t show a thumbnail properly (it has a standard “missing image” icon instead) while the second one works fine.

The underlying cause for this was a mismatch in the duration for which Kerika was caching the thumbnail of an attachment after it had first been retrieved from Google Drive, and how long Google Drive was keeping the thumbnail around.

So you never saw the problem when you first attached an image, but if you went back to the card after 30 days you would see the “missing image” icon instead.

We have fixed this. You may still see this if your browser is caching old thumbnails; you can completely eliminate the problem by clearing your browser’s cache, which would force Kerika to request new thumbnails from Google.

Bug, fixed: the Views count was incorrect in certain situations

Bug Fixes,

We found and fixed a bug that reported incorrect counts for some Views (on the Home page), that was triggered when users did a particular sequence of opening a View, applying the Assigned to Me toggle, and then returning to the Home page.

It was an edge case that took us a while to figure out because our own team didn’t see the problem happen; it only affected a few users.

Views on Home Page
Views on Home Page

The counts shown on your Home Page, under the Views tab, should be correct now.

Bug, fixed: our Pricing Page wasn’t showing up correctly.

Bug Fixes

Thanks to our users in Belgium and Finland for pointing this out to us: our Pricing Page wasn’t displaying correctly in browsers that had their default language set to something other than English.

This was happening only sporadically, and only in Chrome; other browsers like Microsoft Edge were handling it correctly.

Chrome was trying to localize text for non-English users before the language resources were ready; this problem had actually been fixed in the latest version of Polymer  We are using ‘app-localize-behaviour’ of Polymer’s app-localize-behaviour (1.0.2).  Turned out we were a version behind in updating our use of Polymer.

 

Bug, fixed: making sure your Daily Task Summary gets sent at 6AM

Agile & Scrum, Bug Fixes, , , ,

We recently found and fixed an odd bug related to the optional 6AM Daily Task Summary email that you can get from Kerika: if you had toggled the preference setting for this email — from ON to OFF, and back to ON again — the email was getting sent at 8AM instead of 6AM.

Daily Task Reminder
Daily Task Reminder (click for larger image)

Essentially a coding mistake on our part, and one we didn’t notice (and none of our users noticed, either) for a long time because no one would try changing this preference setting very often.

The bug’s been fixed.

Bug, fixed: signing up for Kerika from “.software” domains

Bug Fixes,

With the proliferation of top-level domains we have had to update some of our old code that tried to make sure people were signing up with properly-specified emails.

In the old days, of “.com” and “.org” and other short domain extentsions, this was easy to check at the time someone entered an email address: if it wasn’t properly formatted we could alert the user right away so they didn’t go down a dead-end path.

We can’t do that anymore: new top-level domains are being launched on a regular basis by registry companies and the list of potential domain extensions is no longer finite or easily matched by regular expressions.

We thought we had done these updates a while back, but clearly something slipped through the cracks: people from “.software” domains were unable to sign up as new users.

That’s fixed now.