Geo property of a contact is ignored by Maps after update from 18.0.2 to 18.0.4

[pepeciseaux]

That issue might come from upstream, but I cannot tell. I thought you could simply check on your side and tell them. Corresponding upstream issue report : nextcloud/maps/#401.

Steps & results:

1. Install a fresh up-to-date Nextcloud app (18.0.4) on an up-to-date Yunohost server (tested: same date of this issue report).
2. In NC-Maps, see:
   • All contacts with a geo property (and no adr) are now missing, although they were properly displayed using 18.0.2.

In addition, behaviour is consistent (and that is a good thing) whatever means you try to use to set or reset a geo property:

3. Remove and set back geo property on a contact (using NC-Contacts).
4. or Create a fresh new contact, and add a geo property but no adr (using NC-Contacts).
5. or Import a contact with a geo property but no adr (using NC-Contacts).
6. In NC-Maps, see:
   • Same results as before: missing, but worked in previous version.

Can you reproduce that?

Notes:

• The address book I used had 951 real-life contacts, 45 of which had a geo property (and no adr). All these 45 cards do not appear anymore in Maps, but others are displayed normally.
• I did not try to add or modify a contact by external Carddav client, because no one I have supports geo property.

By the way, geo support is a great unique feature of NC (too bad it vanished on my instance).

[zamentur]

Probably fixed with nextcloud/maps#634

@pepeciseaux Could you confirme we can close it ?