Okay, thank you for the review.
The issue was in the version 2.6.2.5 but it was working normally on my device then. If you look closer to PO's reply, you would agree that he said the same thing. After the issue was reported by that contributor, the Po has released up to 14 builds of the app and the issue surfaced on the version I reported.