alias counter (forwards, replies and blocks) set to 0 (need to refresh) about simple-login-android HOT 8 CLOSED

For now I don't have any idea as refreshing seems to solve the issue as the server doesn't use any cache. Can you check in the server log if you see any error?

from simple-login-android.

For now I don't have any idea as refreshing seems to solve the issue as the server doesn't use any cache. Can you check in the server log if you see any error?

ok found it (kind of). def get_alias(alias_id) returns me the right number, but get_alias_v2 returns me 0 on nb_block, nb_forward, etc. After refreshing the app it must update the db, by getting alias through get_alias(alias_id) ? I'm not good enough in db stuff to completely understand the table/research you have :).

Note get_alias_v2 do return email bounce, forwarded and blocked but count is at 0.

At the end, android app is more a solution than a bug :)

from simple-login-android.

To add up, new email are added to the counter.
For instance, if I have a counter that should have 3 nb_forward pre-4.6.2, and has 0 post-4.6.2, any new forwarded email will increment this counter by 1 (when refreshing from main alias page -the one that displays them all-). So issue seems to be on search term on the API side or on db... :)

from simple-login-android.

The difference between get_alias and get_alias_v2 is the former uses get_alias_infos_with_pagination() whereas the latter uses get_alias_infos_with_pagination_v3 which is also used by the web. Do you see the same issue (i.e. 0 counter) on the web dashboard?

from simple-login-android.

Yes same happens on the web. On global alias page counter are wrong but on individual alias detail (/dashboard/alias_log/X) it is the right number

Tbc counter are not 0 but they restart at 0 from migration to 4.6.2-beta. Detail page shows from real alias creation

from simple-login-android.

Do you mean this one here is wrong?

but the one here is correct?

from simple-login-android.

Exactly. Does it thinks email handled in 3.4.0 are more than 2 weeks old ?
Anyway so much research for this small issue is maybe overkill :)

from simple-login-android.

@Spitfireap that's my only hypothesis for now. Let's see in 2 weeks if this issue magically goes away :)

from simple-login-android.