Ok, let me try to give the steps:
1. Release dump is packaged at version X
2. A week later, an update to search config is published, records and metadata are at version X+1 on the server
3. Browser starts with a fresh profile. Records dump is loaded, signature verification is skipped for this time.
4. Another call to `.get({verificySignature: true})` is made, local DB has records but metadata are still missing, we fetch them to verify the signature. 5. Pulled signature is at version X+1 and local DB is at version X (packaged records dump). Signature verification will fail.
My suggestion would be to go with `b.` at step 4. Synchronize the collection instead of just fetching the missing metadata, so that local DB (records + metadata) will both at version X+1
Bug 1640023 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Ok, let me try to give the steps:
1. Release dump is packaged at version X
2. A week later, an update to the collection is published, records and metadata are at version X+1 on the server
3. Browser starts with a fresh profile. Records dump is loaded, signature verification is skipped for this time.
4. Another call to `.get({verificySignature: true})` is made, local DB has records but metadata are still missing, we fetch them to verify the signature. 5. Pulled signature is at version X+1 and local DB is at version X (packaged records dump). Signature verification will fail.
My suggestion would be to go with `b.` at step 4. Synchronize the collection instead of just fetching the missing metadata, so that local DB (records + metadata) will both at version X+1