I can confirm this, the bug is still present in Pushover 0.0.5