AquaMail Forum
English - Android => Development builds => Topic started by: Kostya Vasilyev on May 03, 2017, 07:51:32 pm
-
https://www.aqua-mail.com/download/AquaMail-market-1.10.0-361-dev-21e48dfb98f5.apk
[ ... other older builds snipped ... ]
https://www.aqua-mail.com/download/AquaMail-market-1.10.0-378-dev-a0dfca94f250.apk
https://www.aqua-mail.com/download/AquaMail-market-1.10.0-379-dev-82e518450598.apk
---
*** Time to start posting new stuff
+ Yahoo: OAUTH2 (their preferred "more secure" login method). To convert an existing account, long press on it -> account setup.
+ Exchange contacts: groups.
+ "Replace names with those from Contacts" now works even when "contact images" are off.
+ Build 366: updated AR translation (thanks, @Paris Geek!)
+ Build 367: new setting: FAB (big round button) color.
+ Build 369: hopefully fix issue with "birthdays" of Exchange contacts.
+ Build 372: contact sync now supports "shared mailbox" (sync with system contacts only, kept "internal contact sync" as it was before)
+Build 373: Samsung S8: use full screen height (by default, no user action needed). Also LG G6 (AFAIK).
+ Build 374: when switching accounts on the compose screen, remove "priority" and "read receipt" if they were enabled in the "old" account, same as we remove "cc / bcc / reply to / greeting / signature". Added animations.
+ Build 378: fixed some UI (visibility) issues with cc / bcc / reply to / priority / read receipt, set from menu and/or set from account's
+ Build 379: workaround for a Firebase push API issue (used in Exchange push)
---
*** Настало время выкладывать что-нибудь новенькое
+ Yahoo: OAUTH2 ("более безопасная" авторизация). Чтобы переключить уже существующую учётную запись, длинное нажатие - основные настройки.
+ Exchange контакты: группы.
+ "Заменять имена отправителей" теперь работает даже если выключены "картинки контактов".
+ Сборка 367: новая настройка: цвет "большой круглой кнопки".
+ Сборка 369: надеюсь что исправлена проблемка с "днями рождений" контактов Exchange.
+ Сборка 372: синхронизация Контактов с системой обрела поддержку "shared mailbox".
+ Сборка 373: Samsung S8: теперь используется полная высота экрана (по умолчанию, настройка не нужна). Также LG G6.
+ Сборка 374: при переключении учёток на экране написания, выключаются "приоритет" и "отчёт о прочтении" если они заданы в "старой" учётной записи (точно также уже убираются "cc / bcc / reply-to / подпись / приветствие). Добавлена анимация.
+ Сборка 378: исправлены проблемы с "неправильной" видимостью полей cc / bcc / reply-to / приоритет / отчет о прочтении.
+ Сборка 379: обход проблемы с Firebase push API (используется Exchange пуш почтой)
-
Re: Unexpected behavior: list is empty (no contacts displayed).
Yes, and actually it's there in 1.9 too.
-
Re: Yes, and actually it's there in 1.9 too.
Fixed in 1.10 build 364.
The QA will decide if it should be merged into 1.9 too (since it took such a long time to find, and it's been there since forever).
-
Version 1.9 was installed. After upgrading to version 1.10, when you click on any notifications, you get to the account, and not to the inbox (as was configured in 1.9)
What settings do I need to change to get into the settings?
Отправлено с моего SM-N930F через Tapatalk
-
Version 1.9 was installed. After upgrading to version 1.10, when you click on any notifications, you get to the account, and not to the inbox (as was configured in 1.9)
I think it's just because you've got unread messages in multiple (> 1) folders. That's how notifications always worked.
-
Version 1.9 was installed. After upgrading to version 1.10, when you click on any notifications, you get to the account, and not to the inbox (as was configured in 1.9)
I think it's just because you've got unread messages in multiple (> 1) folders. That's how notifications always worked.
You was right! Thank you!
Отправлено с моего SM-N930F через Tapatalk
-
Hello Kostya,
I installed this version and I found that:
1. On my tablet with Android 4.4.2, groups work fine.
2. But on my cell phone with Android 7.0, groups don't appear.
Regards.
-
@Hector
The "standard" Contacts app varies from phone to phone / manufacturer / model / Android version.
On my Nexus 5x (Android 7.1), groups are in the "navigation drawer", on the left.
What *not* to expect:
In order to display and edit groups right when you open a contact - the Android Contacts app, no matter what the device, is not capable of doing this for third-party contacts (it only handles this for Gmail and built-in Exchange) - so we'd need to implement our own, complete Contact Editor (and link that into Contacts app).
We have not done that yet.
What *to* expect:
Your list of groups should be accessible / visible, with better UI on some devices (I checked a few that I own, Samsung, Sony, HTC, they all have a tab for Groups) and "not so good" UI on others (e.g. Nexus with standard Google Contacts).
So at the very least, you should be getting your "already established groups, created perhaps in Outlook, as a way to organize your hundreds or thousands of contacts".
Groups are editable on some of those "better" devices, but you'll have to open a group and then "add a contact into it" or "remove a contact". Aqua will sync those edits back to the server, we do have code for that.
-
I understand.
When are you planning to implement the Contact Editor?
Best regards.
-
However, when I am using the Nine app to sync contacts, the group appears in the native contact app. It is a field that I can update.
And after using AM the group appears just in the navigation drawer.
Regards.
-
Since you are in dev mode.. how about davdroid and webdav integration? Calendar, contacts, files? All things we can use without Exchange :-)
Best, Al
-
Um, adding *Dav sync would like adding SMS reading - why would an email app do that?
Besides, there already are apps for CardDAV and CalDAV in Play.
-
Re: However, when I am using the Nine app to sync contacts, the group appears in the native contact app. It is a field that I can update.
Appears how, where? If you "view" and then "edit" a contact? You posted screenshots before.
That's a "custom contact editor plugin" which they've implemented but we obviously haven't.
I don't know when we'll be able to work on that, it's a large task -- and even without it, how things are right now, your "synced by AquaMail" contacts should already be organized into groups.
But also as I wrote above - a lot depends on your phone and its built-in Contacts app.
I found that groups show quite nicely on some phones (checked Samsung, Sony, HTC) 1) there is a way to "view all groups" and 2) vice versa, when "viewing" a contact they show the contact's groups 3) and groups can be edited too (add / remove contact to / from a group).
On Nexus devices groups are much more limited, a deliberate move by Google which made a lot of "noise" back then. But the information is still there synced by Aqua.
What is your phone make / model / Android version?
-
Thanks Kostya. I am not sure about the "custom contact editor plugin", yes, Nine has an app to update their contacts, but I am using the Contact app that comes with my phone. If this app can be updated with a plugin you are right.
I have a Moto G5 Plus, Android 7.0
-
I have another comment. Maybe this issue is something not related to AM, but with Nine it doesn't happen.
If I add a birthday, something happens with the date on my Calendar App that shows the contact birthday for 2 days, instead of just one day. It is something strange because there are other birthdays that are shown with the correct date.
It happens with contacts birthdays added previously and contacts added after using AM to sync contacts.
CalenGoo (the calendar App) takes the contact birthday date and shows it on the top of the day.
I am adding some images:
1. The test contact.
2. The calendar app showing the birthday for 2 days (starting one day before the real date).
3. Outlook showing the correct date.
Regards.
-
Re: I have a Moto G5 Plus, Android 7.0
Moto is pretty much same as Nexus - "pure" Android, and the Contacts app there isn't good with Groups.
Re: birthdays
Yes I see it now.
Must be a side effect of "time zones" and how I'm now storing events (birthdays, wedding anniversaries) in the UTC time zone (I thought this is what Android wanted... and this is how Exchange returns them).
I'll file a bug report.
-
Re: If I add a birthday, something happens with the date on my Calendar App that shows the contact birthday for 2 days, instead of just one day.
I hope this is fixed in build 369 (in this topic header).
-
Thanks. It is working!
Regards...
-
Re: Thanks. It is working!
Good :)
-
Thanks for this dev builds!
I was redirected here following my request if Aqua-mail will support oauth authentication for yahoo account and the answer is yes!
Purchased pro key, I'm testing the 367 build.
Yahoo account seems to work, although sometimes it seems to "fall asleep": sincronization sometimes seems don't happen and in this 2 days I've got also an error in sincronization (I just saw a red exclamation point next to the last sync time). This morning, just turned on my cell phone, all my mail accounts synced, except for yahoo... But during this day it seemed to work properly.
A question: I see that the "push" option is not available for yahoo account. Yahoo does not allow this option or this will be implemented in future?
Thank you for all your great work!
-
Yahoo account seems to work, although sometimes it seems to "fall asleep": sincronization sometimes seems don't happen and in this 2 days I've got also an error in sincronization (I just saw a red exclamation point next to the last sync time). This morning, just turned on my cell phone, all my mail accounts synced, except for yahoo...
That "red last sync time" mean -- that the app tried, but ran into network / connectivity errors. Could be some other thing not OAUTH (remember that OAUTH2 is just a particular way to log in, nothing else).
I'd say keep an eye on it and see how it behaves, write back if this remains.
Re: push
For push mail, for "Internet Mail" (IMAP) accounts, Aqua Mail uses the industry standard, well documented, widely supported "IDLE" extension.
It is supported / used by: Gmail, AOL, Hotmail, Yandex, GMX, Fastmail, Web.de services and others, and also servers like Dovecot, Courier, Cyrus and others.
Yahoo however chose to not implement it. I believe they have their own mechanism for push mail which they'd worked out with Apple and which is undocumented.
-
Hi,
as I'm currently testing Exchange Online, I found that AquaMail is almost the only app that includes the contacts and calendar sync also for shared mailboxes! Thanks for that, great tool!! :-)
One issue I found with the 1.10 dev builds is the contact sync with a shared exchange mailbox account. It seams it is syncing the contacts from the main account, not from the shared mailbox entered in the account settings.
Is this a bug or did I understood this function wrong?
-
One issue I found with the 1.10 dev builds is the contact sync with a shared exchange mailbox account. It seams it is syncing the contacts from the main account, not from the shared mailbox entered in the account settings.
Um, just something I forgot to keep in mind in the contacts code. I'll make a note to fix this.
-
Re: contact sync with a shared exchange mailbox account
Should be fixed in build 372 (the link is above).
-
Have you tested calendar invitations? Would you please tell me if it's working (accept, maybe, decline invitations, sent and received by AquaMail). Thank you
I made some tests between the main Exchange account and the shared mailbox calendar (two separate accounts in AM). As far as I can see everything works as expected.
I use Business Calendar 2 as calendar app, created an appointment on the shared calendar and invited the main account. Invitation was synced correctly to main account calendar and I can switch status there. Status was reflected correctly in the original appointment in shared calendar. Also canceling or declining the appointment/invitation removes it correctly from the calendar.
Not sure if the calendar app has an influence here, or the used mailbox account type. But in my setup it looks fine! :)
-
Re: contact sync with a shared exchange mailbox account
Should be fixed in build 372 (the link is above).
Tested and verified successfully ;)
Thanks alot!
-
Have you tested calendar invitations? Would you please tell me if it's working (accept, maybe, decline invitations, sent and received by AquaMail). Thank you
I made some tests between the main Exchange account and the shared mailbox calendar (two separate accounts in AM). As far as I can see everything works as expected.
I use Business Calendar 2 as calendar app, created an appointment on the shared calendar and invited the main account. Invitation was synced correctly to main account calendar and I can switch status there. Status was reflected correctly in the original appointment in shared calendar. Also canceling or declining the appointment/invitation removes it correctly from the calendar.
Not sure if the calendar app has an influence here, or the used mailbox account type. But in my setup it looks fine! :)
Thank you. Are you accepting /declining meeting invitations in AquaMail attachements? Or you're simply using calendar events in the calendar app to accept /decline them?
Hm, I did all the actions in the calendar app. I will try to repeat it from within AM directly.
-
Have you tested calendar invitations? Would you please tell me if it's working (accept, maybe, decline invitations, sent and received by AquaMail). Thank you
I made some tests between the main Exchange account and the shared mailbox calendar (two separate accounts in AM). As far as I can see everything works as expected.
I use Business Calendar 2 as calendar app, created an appointment on the shared calendar and invited the main account. Invitation was synced correctly to main account calendar and I can switch status there. Status was reflected correctly in the original appointment in shared calendar. Also canceling or declining the appointment/invitation removes it correctly from the calendar.
Not sure if the calendar app has an influence here, or the used mailbox account type. But in my setup it looks fine! :)
Thank you. Are you accepting /declining meeting invitations in AquaMail attachements? Or you're simply using calendar events in the calendar app to accept /decline them?
Hm, I did all the actions in the calendar app. I will try to repeat it from within AM directly.
I created a second account now in Exchange Online and did the test again with this account directly from OWA (without having it in AM or on my phone at all).
Send invitations to the account in AM then from the new account, in AM I opened the invitation mail and used the buttons there to respond. Accept, Decline and Maybe, all replies were shown in the original appointment correctly in the invitators account. In AM I can also see the sent response mails, Accepted:, Declined: and Tentative:.
Was this what you were asking for? It looks like it works correctly, at least between two Exchange accounts.
-
One last thing that would make the Exchange integration perfect ;)
In this thread there was a discussion about allowing "identities" also for Exchange accounts:
https://www.aqua-mail.com/forum/index.php?topic=4940.msg28694#msg28694 (https://www.aqua-mail.com/forum/index.php?topic=4940.msg28694#msg28694)
I think the proposed solution would work, as the same way it is done in Outlook. Are there any plans to add this feature currently? I could easily test it as long as my Exchange Online test period is running :-)
-
I think the proposed solution would work, as the same way it is done in Outlook. Are there any plans to add this feature currently? I could easily test it as long as my Exchange Online test period is running :-)
No we're not working on that right now, sorry.
-
+ Build 374: when switching accounts on the compose screen, remove "priority" and "read receipt" if they were enabled in the "old" account, same as we remove "cc / bcc / reply to / greeting / signature". Added animations.
Not working (Android 7, S7 edge)
1 - For Account A, enable "set priority by default" and "read receipt by default".
2 - For Account B, do not.
3 - Compose
4 - Account A
5 - "priority" and "read receipt" become visible
6 - Switch to Account B
7 - NEW -> "priority" and "read receipt" disappear
There are no animations of anything when things are hidden / shown by switching accounts.
Animations, Android 5.0+
1 - Account A -> tap the "X" on "priority" or "read receipt"
OR
1 - Account B -> Menu -> "Set high priority" or "Request read receipt".
-
+ Build 374: when switching accounts on the compose screen, remove "priority" and "read receipt" if they were enabled in the "old" account, same as we remove "cc / bcc / reply to / greeting / signature". Added animations.
+ Сборка 374: при переключении учёток на экране написания, выключаются "приоритет" и "отчёт о прочтении" если они заданы в "старой" учётной записи (точно также уже убираются "cc / bcc / reply-to / подпись / приветствие). Добавлена анимация.
В версии 374 наблюдается странное, нелогичное поведение:
Установлены адрес Скрытой копии и Обратный адрес (Учётная запись/Доп. настройки и папки/ Написание и отправка):
Вариант 1 - также включен пункт "Отчёт о прочтении":
- При создании нового сообщения поля Скрытая копия и Обратный адрес скрыты (то, что мне ОЧЕНЬ нужно)! Но если выключить в настройках "Отчёт о прочтении", то при написании письма поля Скрытая копия и Обратный адрес становятся снова видимыми.
Вариант 2 - включен пункт "Показывать копию/скрытую копию" (CC/BCC).
- При создании нового сообщения поле Обратный адрес не видно (поля Скрытая копия и копия (пустые или с заданным адресом), потятное дело, видны). И это уже вне зависимости от включенного или выключеного пункта "Отчёт о прочтении".
В связи с этим вопрос - это побочный эффект улучшений для работы с несколькими учётными записями или всё-таки задумывалось следующее?:
- по-умолчанию скрывать установленный в настройках обратный адрес (с возможностью его удаления или замены через меню 3 точки)
- по-умолчанию скрывать установленные в настройках адреса копии и скрытой копии (с возможностью их удаления или замены через меню 3 точки)
В принципе, это логично - если ты настраиваешь эти поля в настройках, то наверняка хочешь иметь (но не видеть) их в каждом письме!
Если планировалось получить именно это, то прошу дать возможность скрывать по-умолчанию эти поля и с выключенным пунктом "Отчёт о прочтении".
Если же это просто "побочка", то очень прошу не исправляйте её!!!!:) Я пока похожу с Отчётом о прочтении))
Спасибо!!!
-
Re: В версии 374 наблюдается странное, нелогичное поведение:
Прошу прощения, это ошибки, влияния на "CC / BCC / Reply-To" не должно быть, эти поля должны работать как раньше.
( извините если Вы не этого хотели, но ошибки есть ошибки, и спасибо за подробное описание, воспроизвёл )
-
Re: В версии 374 наблюдается странное, нелогичное поведение:
Прошу прощения, это ошибки, влияния на "CC / BCC / Reply-To" не должно быть, эти поля должны работать как раньше.
( извините если Вы не этого хотели, но ошибки есть ошибки, и спасибо за подробное описание, воспроизвёл )
Т.е. просто "исправите"? :(
А можно за мою "помощь" добавить в настройки кнопочку "скрыть поля Копия, Скрытая копия, Обратный адрес (даже если для них заданы адреса). Или напротив каждого поля. Ведь, как видим, это можно сделать, хоть и случайно.
И повторю свою мысль: Это же логично - если человек настраивает эти поля в настройках, то наверняка он хочет иметь (но не видеть) их в каждом письме!
Если нет, то буду сидеть на версии 376, пока не реализуете эту возможность на желаемом Вами уровне....
-
А можно за мою помощь добавить в настройки кнопочку "скрыть поля Копия, Скрытая копия, Обратный адрес (даже если для них заданы адреса). Или напротив каждого поля. Ведь, как видим, это можно сделать, хоть и случайно.
Пока что такое не планируется. Есть опасение что люди будут путаться.
-
А можно за мою помощь добавить в настройки кнопочку "скрыть поля Копия, Скрытая копия, Обратный адрес (даже если для них заданы адреса). Или напротив каждого поля. Ведь, как видим, это можно сделать, хоть и случайно.
Пока что такое не планируется. Есть опасение что люди будут путаться.
Понял, "буду сидеть на версии 376, пока не реализуете эту возможность на желаемом Вами уровне...."
P.S. Кстати, про "путаться". Я всё время путаюсь где "BCC", а где "Reply-To" (чтобы одно из них удалить или когда нужно тот же адрес, что в BCC, поставить в BC). Чтобы понять, где что, нужно удалить адрес. Хорошо было бы сделать постоянные аккуратные ярлычки слева от адреса - "cc", "bcc", "re" ("CC", "BCC", "RE") например.
-
Tried 378 but it crashes on startup for me:
E/AndroidRuntime( 4894): FATAL EXCEPTION: EwsPushManager
E/AndroidRuntime( 4894): Process: org.kman.AquaMail, PID: 4894
E/AndroidRuntime( 4894): java.lang.NullPointerException
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.h.a(SourceFile:117)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.m.a(SourceFile:192)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.a.a(SourceFile:511)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.z.b(SourceFile:619)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.z.a(SourceFile:331)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.z.a(SourceFile:57)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.ab.run(SourceFile:1259)
E/AndroidRuntime( 4894): at android.os.Handler.handleCallback(Handler.java:733)
E/AndroidRuntime( 4894): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 4894): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 4894): at android.os.HandlerThread.run(HandlerThread.java:61)
EDIT: 361 crashes with the same stacktrace.
-
P.S. Кстати, про "путаться". Я всё время путаюсь где "BCC", а где "Reply-To" (чтобы одно из них удалить или когда нужно тот же адрес, что в BCC, поставить в BC). Чтобы понять, где что, нужно удалить адрес. Хорошо было бы сделать постоянные аккуратные ярлычки слева от адреса - "cc", "bcc", "re" ("CC", "BCC", "RE") например
Так они там есть, под кнопкочками выбора контактов, как раз слева. Может быть Вы их выключили "для экономии места"?
Tried 378 but it crashes on startup for me:
E/AndroidRuntime( 4894): FATAL EXCEPTION: EwsPushManager
E/AndroidRuntime( 4894): Process: org.kman.AquaMail, PID: 4894
E/AndroidRuntime( 4894): java.lang.NullPointerException
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.h.a(SourceFile:117)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.m.a(SourceFile:192)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.a.a(SourceFile:511)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.z.b(SourceFile:619)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.z.a(SourceFile:331)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.z.a(SourceFile:57)
E/AndroidRuntime( 4894): at org.kman.AquaMail.mail.ews.push.ab.run(SourceFile:1259)
E/AndroidRuntime( 4894): at android.os.Handler.handleCallback(Handler.java:733)
E/AndroidRuntime( 4894): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 4894): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 4894): at android.os.HandlerThread.run(HandlerThread.java:61)
Will check, thank you.
-
Re: Tried 378 but it crashes on startup for me:
Does your phone have Google Play Services installed?
Is it up to date?
Does the phone have connection to the Internet?
-
Re: Tried 378 but it crashes on startup for me:
Please try 379 posted above.
-
P.S. Кстати, про "путаться". Я всё время путаюсь где "BCC", а где "Reply-To" (чтобы одно из них удалить или когда нужно тот же адрес, что в BCC, поставить в BC). Чтобы понять, где что, нужно удалить адрес. Хорошо было бы сделать постоянные аккуратные ярлычки слева от адреса - "cc", "bcc", "re" ("CC", "BCC", "RE") например
Так они там есть, под кнопкочками выбора контактов, как раз слева. Может быть Вы их выключили "для экономии места"?
Не смог найти такую пункт, хотя помню, что подобное отключал. Подскажите, пожалуйста, в каком разделе настроек это находится?
P.S. Какой смысл жать кнопку "Выбрать контакт" и попадать в поле вписывания/поиска имени контакта (лишнее движение), если поля Кому/CC/BCC сразу являются интерактивными полями поиска контактов? Сделано в угоду любителей листать списочки?:)
-
Re: Не смог найти такую пункт, хотя помню, что подобное отключал. Подскажите, пожалуйста, в каком разделе настроек это находится?
Настройки программы - работа с контактами.
Кстати, на экране настроек есть поиск :)
Re: Какой смысл жать кнопку "Выбрать контакт"
Выбор больше одного контакта за раз. Группы.
Если лично Вам не нравится - можете не нажимать :)
-
Re: Не смог найти такую пункт, хотя помню, что подобное отключал. Подскажите, пожалуйста, в каком разделе настроек это находится?
Настройки программы - работа с контактами.
Выглядит как надо (маленькие, аккупатненькие cc, bcc, repl (было бы лучше просто re) )!:)
Но всё равно ПРОШУ оставлять эти надписи и без кнопок выбора контактов(((
-
смысл жать кнопку "Выбрать контакт"
Выбор больше одного контакта за раз. Группы.
Если лично Вам не нравится - можете не нажимать :)
При "встроенном выборе" контактов проявляется одна недоработка (отсутствие возможности) - нужно дать возможность менять формат отображения имени контакта - Имя (Отчество), Фамилия (как сейчас везде) или Фамилия, Имя (Отчество). Это должно распространяться на всё - список писем, список контактов при выборе, имя в просмотре сообщения, имя в новом письме.
И еще при "встроенном выборе контактов" имя контакта не отображается в 2 строки. А форма поиска контактов и так Уже экрана.
Кстати, что далеко ходить - системный выбор контактов на Samsung S6 - Фамилия, Имя (как выбрано для контактов) и имя в 2 строки
-
Re: При "встроенном выборе" контактов проявляется одна недоработка
Согласен. Ну нет в мире совершенства :)
-
Re: При "встроенном выборе" контактов проявляется одна недоработка
Согласен. Ну нет в мире совершенства :)
Смешно:)
-
Re: Tried 378 but it crashes on startup for me:
Please try 379 posted above.
379 works, thanks!
Yeah I'm connected to the internet, 3G. Google Play Services 1084000. I upgraded from 1.9.0-316-dev-1cc5c37ef3ee which didn't crash.
-
Re: 379 works, thanks!
Thanks for confirming!
-
Spoke too soon. Notifications don't work anymore. Looks like you've switched to using Firebase for notifications, which my phone does not support. That's OK, I'll stay on 1.9.0. Thanks.
-
Spoke too soon. Notifications don't work anymore. Looks like you've switched to using Firebase for notifications, which my phone does not support. That's OK, I'll stay on 1.9.0. Thanks.
... mh, notifications are still working also with version 1.10.0.379-dev (... 1.10.0.382-dev).
Could you describe your issue more specifically please?
-
If I have to guess:
AquaMail must be using new versions of the FCM/GCM libraries (i.e. changed similarly to https://github.com/vector-im/riot-android/commit/15bba9dce4a96e49fd4bd5132e2f60b57bdf1059) These new versions are broken on my phone. This is because I'm not using Google's Play Services, but a reimplementation of them.
So, notifications (presumably) work fine except in my particular phone, because of the way I have it set up, and I don't expect anyone to fix it for me. I do appreciate Kostya fixing the crash, as now I have a test case I can use to potentially fix my version of Play Services.
Apologies if I sounded like I meant to imply otherwise. Thanks.
-
If I have to guess:
AquaMail must be using new versions of the FCM/GCM libraries. These new versions are broken on my phone. This is because I'm not using Google's Play Services, but a reimplementation of them.
So, notifications (presumably) work fine, except in my particular phone, because of the way I have it set up, and I don't expect anyone to fix it for me. I do appreciate Kostya fixing the crash, as now I have a test case I can use to potentially fix my version of Play Services.
Apologies if I sounded like I meant to imply otherwise. Thanks.
Thanks for your feedback and clarification.
-
Yes we did switch the low-level push transport from GCM (deprecated by Google) to Firebase Cloud Messaging (current, supported).
Just to be clear since Firebase is a dozen or more different technologies under one "umbrella":
- We do not use Firebase Notifications
- Or Firebase Analytics
- Or Firebase anything else
Just the low-level technology for "server sends a short data message to the app on a specific device and it gets delivered by Google's cloud magic".
Re: This is because I'm not using Google's Play Services, but a reimplementation of them
Sorry about this, no idea such things existed.
Oh and it would be a good idea for this "reimplementation" to throw an exception from Firebase.getToken if that's not supported. Remember the crash? On your phone getToken returned "null" and no exception. Bad.