Page MenuHomePhabricator

[native] remove device ID getter and setter functions
ClosedPublic

Authored by varun on Oct 20 2023, 9:40 AM.
Tags
None
Referenced Files
F3192637: D9556.id32436.diff
Fri, Nov 8, 10:04 PM
F3192636: D9556.id32284.diff
Fri, Nov 8, 10:04 PM
F3192514: D9556.id.diff
Fri, Nov 8, 10:01 PM
Unknown Object (File)
Tue, Nov 5, 2:13 AM
Unknown Object (File)
Tue, Oct 29, 2:52 PM
Unknown Object (File)
Oct 2 2024, 1:59 PM
Unknown Object (File)
Sep 19 2024, 10:47 AM
Unknown Object (File)
Sep 19 2024, 10:45 AM
Subscribers

Details

Summary

a device's ID is their content ed25519 signing public key. this gets created when the content olm account is created in the CryptoModule.

it seems like we can safely deprecate getDeviceID and setDeviceID and remove the callsite in sqlite-data-handler.js

Test Plan

successfully ran the app. tried logging in and out, registering and deleting an account. everything worked fine.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Oct 20 2023, 9:43 AM
Harbormaster failed remote builds in B23408: Diff 32284!

apparently we use native/cpp files on web? @kamil can you please make sure this update is correct? i ran yarn build-db-wasm

In D9556#280174, @varun wrote:

apparently we use native/cpp files on web?

Yes, those are WASM bindings and the files are web-specific.

@kamil can you please make sure this update is correct? i ran yarn build-db-wasm

Running yarn build-db-wasm and committing generated files is everything that needs to be done, looks okay.

Do we have to keep rust and web code, or also can be removed?

This revision is now accepted and ready to land.Oct 25 2023, 3:31 AM

Do we have to keep rust and web code, or also can be removed?

addressed in follow up diff