Hi, hAppreciator! That's indeed a bug, but we fixed it and we are rolling out the fix with the next update.
