AquaMail Forum

English - Android => Development builds => Topic started by: Kostya Vasilyev on March 31, 2015, 02:11:36 am

Title: 1.5.5.8
Post by: Kostya Vasilyev on March 31, 2015, 02:11:36 am: http://www.aqua-mail.com/download/AquaMail-market-1.5.5.8.apk

---

+ Updated translations

+ Fixed issue in Calendar sync related to PrivacyGuard / XPrivacy

Not in Google Play.

Gmail's OAUTH seems to be broken on Google's side, not able to refresh access token, resulting in access errors (seen i the UI as ServerError, NetworkError). This is literally in the last hour.

---

+ Обновленные переводы

+ Исправил проблему в синхронизации календаря при использовании PrivacyGuard / XPrivacy

Не в Google Play.

У Гугла что-то творится с авторизацией через OAUTH, в Аквe, в учетных записях Gmail, выскакивает ServerError, NetworkError. Буквально в течение последнего часа.
Title: Re: 1.5.5.8
Post by: Kostya Vasilyev on March 31, 2015, 05:52:26 pm: Yep, first IMAP and then OAUTH.

On the other hand, it looks like they fixed the issue with flags, just a few days after the report:

http://mailman13.u.washington.edu/pipermail/imap-protocol/2015-March/002480.html

PS - does K9 now support OAUTH? It's still "open" in their bug tracker:

https://code.google.com/p/k9mail/issues/detail?id=6066
Title: Re: 1.5.5.8
Post by: bkcfunk on April 01, 2015, 07:00:36 pm: So there is no update on Gmail yet right? It takes a minute after my email sync
Title: Re: 1.5.5.8
Post by: Kostya Vasilyev on April 01, 2015, 09:23:04 pm: >> So there is no update on Gmail yet right

Update regarding what?

>> It takes a minute after my email sync

Um, couldn't parse that, sorry???
Title: Re: 1.5.5.8
Post by: Kostya Vasilyev on April 01, 2015, 11:35:21 pm: I just noticed that in my Gmail account on the iPhone -- in the built-in Email app -- the count of unread messages is wrong, marking messages as read doesn't propagate, but the count is wrong even if I adjust for those....

Not seeing anything strange in Aqua 1.5.5, but 1.5.1 could be getting confused too.

I assume it's same issue, continuing:

http://mailman13.u.washington.edu/pipermail/imap-protocol/2015-March/002480.html