Version 1.7.1-88 - "stable" - full Google Play release

[Kostya Vasilyev]

@steveab:

Can you remind me your phone's "Exchange Push Device ID", it's in app settings -> debug, very end? Tapping the list item will copy the value to the clipboard.

[nadir husain]

@Paris Geek
How is the push on your nougat enabled phone?

[nadir husain]

@Paris Geek thanks for the info 

[stevealb]

@steveab:

Can you remind me your phone's "Exchange Push Device ID", it's in app settings -> debug, very end? Tapping the list item will copy the value to the clipboard.

Exchange push device id:
ac5d081abe7daab1314b65269fed7c38fbad86c6

[Kostya Vasilyev]

---
Unexpected behavior:
- "REPLY" in not displayed in message notification
---

This is normal.

---
Unexpected behavior:
- "Move to deleted" in notification will not ask for confirmation. Action is executed immediately
---

I'll take a look.

---
Exchange push device id:
ac5d081abe7daab1314b65269fed7c38fbad86c6
---

Thank you.

Checked server logs, any mailbox changes are routed to the app over GCM as soon as they're received from Exchange, within about 3-5 seconds.

It's conceivable that there could be delays in the GCM machinery, I've seen these on my phones (before, while still developing this feature, sometimes up to 5 minutes or more).

[Kostya Vasilyev]

Unexpected behavior:
- "REPLY" in not displayed in message notification

Fixed:

http://www.aqua-mail.com/forum/index.php?topic=5239.0

Unexpected behavior:
- "Move to deleted" in notification will not ask for confirmation. Action is executed immediately

Darn. This one's a bitch, there is no way that I'm aware of to know where a notification action comes from (Android 7's "status bar" notifications *are* Android Wear notifications).

[Kostya Vasilyev]

The latest build 1.7.1-93 works correctly with Genymotion/Ubuntu as far as Exchange push is concerned => Exchange push works now as expected in all environements/devices I use.

Good to hear, thank you.

I have to assume that Genymotion fixed something in their emulator, or maybe (gasp!) Google did, since there were no changes in the app this recently.

[Kostya Vasilyev]

Kostya, still a bug in v1.8
If this is hard to fix, please consider not selecting by default "Smart Watch enhancements". I've noticed that unselecting "Smart watch enhancements" is a workaround.

It is, and still is in the bug tracker.

The issue here is that Android 7's "improved notifications", which they are -- *are* Android Wear notifications.