-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Birthday import for contacts may not work #45
Comments
Hi, thanks for the bug report. There are 2 types of birthdays in VCard format: date and text. When you set an incomplete date in google contacts, it actually sets a text birthday. Nextcloud Contacts does not support text birthdays. That leaves us with 2 options:
|
Signed-off-by: Julien Veyssier <eneiluj@posteo.net>
Hi, I speculate, there are chances to pass the "text dates without a year" from Google to Nextcloud doing a proper conversion to a date format first for the following reasons:
Although, this might not address all "text date issues". |
Signed-off-by: Julien Veyssier <eneiluj@posteo.net>
You're very right, it is possible to add incomplete birthdays! Best thing is it is simple to get from Google API response. If it was entered correctly on google side (with the format corresponding to user's locale, then the API provides month and day attributes instead of a raw text (that would be impossible to parse not knowing the locale). This app now uses the standard way to omit the year in the created VCard. It is displayed correctly in Contacts. Yay! |
I did superficial testing with one contact. It worked. Thank you. |
As a nextcloud user I wanted to port my contacts from "Google Contacts".
Some contacts ended up without the birthday field in the user interface and also the calendar app did not show their birthdays. For other contacts, the port of the birthday field worked.
Preliminary research makes me assume, that this behavior might be related to the missing year of birth. For contacts with a year of birth, things seemed to work. For contacts with only day and month of birth, there seems to be a problem. Although, I only went through few contacts to back this hypothesis.
Just thought, I leave this here as a possible issue. Thanks for writing this software, anyway =).
The text was updated successfully, but these errors were encountered: