Page MenuHomePhabricator

Write to temporary message storage from NotificationService
ClosedPublic

Authored by marcin on Jul 5 2022, 4:53 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 23, 3:48 AM
Unknown Object (File)
Sat, Nov 2, 5:29 PM
Unknown Object (File)
Sat, Nov 2, 11:15 AM
Unknown Object (File)
Sat, Nov 2, 11:15 AM
Unknown Object (File)
Sat, Nov 2, 11:15 AM
Unknown Object (File)
Sat, Nov 2, 11:15 AM
Unknown Object (File)
Sat, Nov 2, 11:15 AM
Unknown Object (File)
Sat, Nov 2, 11:15 AM

Details

Summary

In this differential TemporaryMessagesStorage API is used in NotificationService to persist messages before they are written to SQLite.

Test Plan

In the debugger we can track execution to ensure no exception is thrown.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

marcin requested review of this revision.Jul 5 2022, 5:57 AM

Remove call to non-existing ensureLockNotHeld method

Rename Temporal to Temporary

marcin retitled this revision from Write to temporal message storage from NotificationService to Write to temporary message storage from NotificationService.Jul 7 2022, 7:14 AM
marcin edited the summary of this revision. (Show Details)
tomek added inline comments.
native/ios/NotificationService/NotificationService.mm
20–23 ↗(On Diff #14279)

Should we check if messageInfos field is there?

This revision is now accepted and ready to land.Jul 7 2022, 8:23 AM
native/ios/NotificationService/NotificationService.mm
20–23 ↗(On Diff #14279)

We did so in differential that wrote to SQLite directly from NotificationService (https://phab.comm.dev/D4063), which was accepted. Therefore it is reasonable to do so here as well.

Check against empty message

This revision was landed with ongoing or failed builds.Jul 20 2022, 6:18 AM
This revision was automatically updated to reflect the committed changes.