Contact syncing not working on Android with some contact apps #6568
Comments
dorianve
added
the
bug
|
HI |
|
Hi, Thanks for your answer. I see the issue was closed but the bug remains: the contacts created in the tuta app are not showing in the phone contact list. Since the contacts were not syncing, I was looking around and found it odd no 'sync element' was showing in the Android Sync settings. I thought it was probably not the expected behaviour, and maybe an indication of where the bug was stemming from, but since it's expected: what do you think could be the cause for the tuta contacts not showing in the phone contact app, then? If it wasn't clear, the article on the tuta blog describes the expected behaviour "creating a contact in your Tuta account will automatically sync to your device contacts". Tuta blog article: https://tuta.com/blog/full-device-contact-integration-is-here |
|
Hey, sorry for misunderstanding. |
|
This is not an isolated issue, I unfortunately have the same problem. Issue: Contact synchronisation is activated in Tuta android app, yet contacts are not appearing in my phone's contacts app. Specifically, I have tried viewing contacts in both my OS default contacts app (Google Contacts) and in an F-Droid downloaded contacts app called 'Fossify Contacts'. Neither has any contacts from Tuta appearing. Device: Oppo A54 5G Currently I'm on the free plan (moving to revolutionary plan soon when my current custom domain email hosting package with another provider ends - I will update if anything changes) |
|
Hi, I'm also using fossify Phone and Contacts, and Tuta is not showing as synced account in the filter list. The default Google Contacts app that came with the device was disabled, but I reenabled it temporarily to see what was happening. And, there, in my case, Tuta contacts actually do show up. I found that surprising and digged a little in the direction of fossify. It appears that it has open issues related to synced contact account not showing (the issue is accounted for since "Simple Contacts" Fossify was forked from). So, maybe the issue is on Fossify's side? But then again, @SteamPumkin just mentionned having the issue with the default Google app ⬆️ |
|
@dorianve you're absolutely right. I thought they weren't showing in Google Contacts but I must have not checked properly/not realised it was merging my Google and Tuta duplicate contacts. I've just re-enabled my Google Contacts app and checked and Tuta contacts are showing there. Good find! This issue must in fact be with the Fossify Contacts/Phone/Messages apps, please disregard. |
|
We are writing "raw contacts" to Android to a separate account from Google. Android is designed to merge raw contacts from different sources into a user-visible "contact". If you want to see only tuta info you should filter by an account in your contacts app. |
|
Hi, The app add a Tuta account in Android settings, but it doesn't synchronize and there is no possibilty to activate it. Edit: same thing with GrapheneOS on Pixel 6a |
|
I can confirm that I have same issue on my GrapheneOS (Pixel 6 PRO) . For now Tuta only sync changes makes in Tuta > Contact app . Enabled sync in Tuta app ✅ in my default GOS contacts app from menu > Create contact > In the option to "Save to" I see only Device or Gmail . Tuta is missing ? Also Tuta account is missing from Contact app and , when I try to add manualy nothing happen, just send to previos screen with no tuta added . |
|
Hi, we plan to look into this issue soon, it looks like some contacts apps don't let you save to Tuta account but some do (like Google Contacts) and we need to investigate what is missing |
charlag
changed the title
charlag
added
goal: mobile integration
feature: phone book
android
charlag
changed the title
Certain contact apps require the account to be syncable. In order to do this, we implement a stubbed sync service and adapter which does nothing and ask Android not to call it. Preexisting installations of the app will need to turn contact synchronization off and on again to receive this fix. Closes #6568. Co-authored-by: paw <[email protected]>
Certain contact apps require the account to be syncable. In order to do this, we implement a stubbed sync service and adapter which does nothing and ask Android not to call it. Preexisting installations of the app will need to turn contact synchronization off and on again to receive this fix. Closes #6568. Co-authored-by: paw <[email protected]>
Certain contact apps require the account to be syncable. In order to do this, we implement a stubbed sync service and adapter which does nothing and ask Android not to call it. Preexisting installations of the app will need to turn contact synchronization off and on again to receive this fix. Closes #6568. Co-authored-by: paw <[email protected]>
Certain contact apps require the account to be syncable. In order to do this, we implement a stubbed sync service and adapter which does nothing and ask Android not to call it. Preexisting installations of the app will need to turn contact synchronization off and on again to receive this fix. Closes #6568. Co-authored-by: paw <[email protected]>
Certain contact apps require the account to be syncable. In order to do this, we implement a stubbed sync service and adapter which does nothing and ask Android not to call it. Preexisting installations of the app will need to turn contact synchronization off and on again to receive this fix. Closes #6568. Co-authored-by: paw <[email protected]>
A small catch that wasn't in the test notes: in Tuta, you have to log in again to have it sync. It's not instant. This is correct behavior, though. |
|
This still doesn't work on Grapheneos. (With the fixed version released today) Everything is the same as was reported originally. (Only 1 way sync tuta>contacts works). Logging in, out, uninstalling/reinstalling the app... It doesn't work. Tuta has all of the authorizations, including contacts, enabled. Please reopen this issue. |
|
@Mangoes |
It works with the Fossify contacts. But not with the Grapheneos default contacts. I also see that the Grapheneos contacts only appears to create the contacts on the device (there is no mention of the tuta account in the contacts app settings, but clicking on the accounts option in the contacts app settings > it opens the system accounts settings and the tuta account is there). In the Grapheneos contacts app settings, there is an option to select the default account for newly created contacts, but the only option available is "on device". |
|
Like @Mangoes , I too am using GrapheneOS Contacts with Tuta and finding that sync occurs only one-way: from Tuta to Contacts. For example:
Like @Mangoes , I also find that the GrapheneOS Contacts app allows me to choose which account to save a new contact to, but it shows no option for Tuta. This happens even though Tuta shows as one of my accounts under Phone Settings > Passwords, passkeys and autofill > Accounts for [user] |
|
Tried the latest version, disabled and reenabled sync, but Tuta doesn't appear as an option for saving contacts in neither Samsung Contacts or Fossify contacts. In Samsung contacts, Tuta contacts appear uneditable but show their source. Fossify instead attributes them to whatever messaging app they have, my tuta account only appears as a source if the contact doesn't use any messaging app, in which case when tapping on the source, it displays the usual list without Tuta (as in, no option is actually marked since it recognizes it being in Tuta) |
|
@charlag Why is this bug still marked as closed? Or should we open a new issue? |
|
I would suggest asking GrapheneOS devs what heuristics they use for showing contact sync providers. It could be that there's something also wrong on our side but it would need some investigation and if there's something to fix on our side I would open another issue. |
|
GrapheneOS uses the standard AOSP Contacts app with very few changes beyond adding support for our Contact Scopes feature, dark mode and vCard v4. We plan to overhaul the appearance of the user interface with Material You soon but we haven't needed to change anything under the hood beyond Contact Scopes support. We didn't change anything about how it handles additional providers and it should work fine. It definitely works with sandboxed Google Play which we've tested and a few other providers. |
|
I did some digging into AOSP and if I understand it right then it looks for certain properties in the manifest: which is further confirmed by this SO answer: so I think we need to experiment with AOSP app or a fork of such and declaring more things in the manifest. |
|
I observe exactly the same situation using Google Contacts on two Samsung devices (a smartphone and a tablet) both running Android 14 One UI 6.1. |
|
@marcosdiasalves I wanted to write that we never had a problem with Google Contacts but I could not actually get it to work now. We will look into that. |
I will request features on forum or via support.
Bug in mobile app
Describe the bug
I wanted to try the new "contact syncing feature" that was presented in a blog post, I activated the setting, but contacts are not syncing.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The contacts should sync.
Screenshots
Smartphone (please complete the following information):
Additional context
"Revolutionary" plan
I will be happy to provide more context if needed, please tell me what you need.
Test notes
Test on an Android device with Fossify Contacts installed. Turn contact synchronization off if it is already on.
The text was updated successfully, but these errors were encountered: