My Docs uses MY_DOCS ordinal (3), not enum id (4)

Ya: 7 Julai 2026, 02:01 UTC
Mwandishi: kamo
Ahadi ya: d18ad86

The backend resolves ImageAssocType via `values()[assocType]` (ordinal index) and persists it @Enumerated(ORDINAL). Every imaging surface passes the ordinal, but the My Docs doc-manager passed the enum's explicit id (4). Ordinal 4 is MEET_RECORDING, so My Docs documents were stamped assoc_id=4 and resolved to the non-existent imaging-meet-recordings bucket instead of imaging-mydocs — making them un-downloadable, un-convertible, and un-editable (edit showed "Document not converted"). Their bytes were always in imaging-mydocs. Use ordinal 3 (MY_DOCS).

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru Milele Mtazamo wa bei