Browse Source
Org policy JSON responses never included a revisionDate field, unlike every other synced entity. The official Bitwarden server always sets it, and current official clients (recently migrated to the WASM SDK's typed PolicyView) now assume it is always a valid date string. Its absence deserializes to undefined client-side, which then throws (RangeError: Invalid time value) when the client formats it, breaking the whole policy sync pipeline and silently emptying the vault view in the browser and desktop apps. Adds a revision_date column (mirroring the existing pattern used by Send), stamped on creation and bumped on every save.pull/7571/head
8 changed files with 19 additions and 5 deletions
@ -0,0 +1,2 @@ |
|||||
|
ALTER TABLE org_policies |
||||
|
ADD COLUMN revision_date TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP; |
||||
@ -0,0 +1,2 @@ |
|||||
|
ALTER TABLE org_policies |
||||
|
ADD COLUMN revision_date TIMESTAMP NOT NULL DEFAULT now(); |
||||
@ -0,0 +1,2 @@ |
|||||
|
ALTER TABLE org_policies |
||||
|
ADD COLUMN revision_date DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP; |
||||
Loading…
Reference in new issue