nextcloud / maps

🌍🌏🌎 The whole world fits inside your cloud!
https://apps.nextcloud.com/apps/maps
GNU Affero General Public License v3.0
504 stars 88 forks source link

[Bug]: nextcloud maps cause nextcloud contact Address field to be limited to 254 characters and error Unable to update contact #1303

Open guerby opened 3 months ago

guerby commented 3 months ago

⚠️ This issue respects the following points: ⚠️

Bug description

If you don't have nexcloud maps installed, defining in nextcloud contact an Address (ADR) of more than 255 characters works fine.

However if you have nextcloud maps installed then defining in nextcloud contact an Address (ADR) of more than 255 characters is refused with an error "Unable to update contact", and in database logs you get:

2024-08-05 12:47:10.397 CEST [149340] ERROR:  value too long for type character varying(255)
2024-08-05 12:47:10.397 CEST [149340] STATEMENT:  INSERT INTO "oc_maps_address_geo" ("adr", "adr_norm", "object_uri", "lat", "lng", "looked_up") VALUES($1, $2, $3, $4, $5, $6)

Steps to reproduce

  1. add a contact with an address field of more than 255 characters (with maps installed)
  2. nextcloud reports an error and does not update the address field

Expected behavior

No error

Installation method

None

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install of the server?

None

Is this bug present after an update or on a fresh install of the app?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

Configuration report

No response

List of activated Apps

$  php occ app:list
Enabled:
  - activity: 2.21.1
  - admin_audit: 1.19.0
  - announcementcenter: 6.8.1
  - app_api: 2.7.0
  - calendar: 4.7.14
  - call_summary_bot: 1.2.0
  - checksum: 1.2.4
  - circles: 29.0.0-dev
  - cloud_federation_api: 1.12.0
  - collectives: 2.13.0
  - comments: 1.19.0
  - contacts: 6.0.0
  - contactsinteraction: 1.10.0
  - dashboard: 7.9.0
  - dav: 1.30.1
  - deck: 1.13.1
  - drawio: 3.0.2
  - event_update_notification: 2.4.0
  - external: 5.4.0
  - externalportal: 1.3.1
  - federatedfilesharing: 1.19.0
  - federation: 1.19.0
  - files: 2.1.0
  - files_accesscontrol: 1.19.1
  - files_antivirus: 5.5.7
  - files_downloadlimit: 2.0.0
  - files_external: 1.21.0
  - files_fulltextsearch: 29.0.0
  - files_pdfviewer: 2.10.0
  - files_reminders: 1.2.0
  - files_sharing: 1.21.0
  - files_trashbin: 1.19.0
  - files_versions: 1.22.0
  - firstrunwizard: 2.18.0
  - forms: 4.2.4
  - fulltextsearch: 29.0.0
  - fulltextsearch_elasticsearch: 29.0.1
  - integration_excalidraw: 2.2.0
  - integration_giphy: 1.0.11
  - logreader: 2.14.0
  - lookup_server_connector: 1.17.0
  - maps: 1.4.0
  - nextcloud-aio: 0.6.0
  - nextcloud_announcements: 1.18.0
  - notes: 4.10.1
  - notifications: 2.17.0
  - notify_push: 0.7.0
  - oauth2: 1.17.0
  - password_policy: 1.19.0
  - photos: 2.5.0
  - polls: 7.1.4
  - privacy: 1.13.0
  - provisioning_api: 1.19.0
  - recommendations: 2.1.0
  - related_resources: 1.4.0
  - richdocuments: 8.4.4
  - serverinfo: 1.19.0
  - settings: 1.12.0
  - sharebymail: 1.19.0
  - spreed: 19.0.7
  - support: 1.12.0
  - survey_client: 1.17.0
  - systemtags: 1.19.0
  - tables: 0.7.5
  - tasks: 0.16.0
  - text: 3.10.1
  - theming: 2.4.0
  - twofactor_backupcodes: 1.18.0
  - twofactor_totp: 11.0.0-dev
  - twofactor_webauthn: 1.4.0
  - user_saml: 6.2.0
  - user_status: 1.9.0
  - viewer: 2.3.0
  - weather_status: 1.9.0
  - welcome: 1.2.0
  - workflowengine: 2.11.0
Disabled:
  - bruteforcesettings: 2.9.0
  - encryption: 2.17.0
  - suspicious_login: 7.0.0
  - user_ldap: 1.20.0

Nextcloud Signing status

No response

Nextcloud Logs

No response

Browser Console

No response

Additional info

I discovered this while importing a VCF into nextcloud, it refused to import a few entries and the common cause was the length of the address field in vcard and having maps app installed on nextcloud