AquaMail Forum
English - Android => Bug reports => Topic started by: Philip on June 24, 2016, 12:23:21 am
-
I have a number of AquaMail Counter widgets on my home screens, one for each of my accounts and one each for ALL and for the SMART folder.
At present, the ALL widget shows a message count of 82 and the SMART shows a count of 8 (covering the last 3 days).
However, when I click on the ALL widget, it shows me the SMART folder (with 8 messages in it) and not ALL my messages (i.e. 82).
I have tried recreating a new ("AquaMail counter") widget with the account set to "[All accounts]" and "Only unread" unticked, and clicking on it displays the SMART folder, not ALL messages, as I would expect.
Running Aqua Mail V1.6.2.5 on a Nexus 6 Marshmallow 6.0.1.
Is this a bug or a feature?
-
The "Unread counter" on the top right corner of the [All accounts] widget shows only the number of the unread messages from the Smart folder.
Indeed this is not what the user expect to see on this widget.
Thanks for your feedback.
@Kostya, can you please have a look into this matter or give us a short explanation of the reason for this.
Thanks a lot.
Mikeone
-
Re: I have tried recreating a new ("AquaMail counter") widget with the account set to "[All accounts]" and "Only unread" unticked, and clicking on it displays the SMART folder, not ALL messages, as I would expect.
Unable to reproduce (repeated all the steps above).
Tapping the widgets runs the app's main screen, account list, and each account having unread messages is expanded. This is exactly how it's supposed to work.
Do you, by any chance, have the app set to "start up in" --> "the smart folder"? App settings -> look and feel.
-
Assuming this is a "yes":
Do you, by any chance, have the app set to "start up in" --> "the smart folder"? App settings -> look and feel.
Fixed. Thank you.
-
Apologies for the delay in replying - I have been away, staying in a hotel that had very sporadic internet access!
Yes, I did have "start up in" set to "smart folder", and I can confirm that version 1.6.2.5-6 fixes the issue.
As always, many thanks for such a speed identification, and resolution, of the problem.