♟ marcin

Add missing privacy API declarations and upgrade MMKV

rebase before landing

I think it is good to add a transaction here as it will force accounts states in SQLite to be in sync.

Force already logged in ETH users to create and sign backup message

Extract shareable logic from CreateSIWEBackupMessage component

Implement screen to create backup mesage and its signature

Persist SIWE backup secrets to SQLite after succesfull registration process

Implement JSI getter and setter for siwe backup secrets

Handle backup message type with different user texts in siwe.reac.js

Introduce user texts for siwe backup message creation

Introduce SIWE message types

rebase before landing

Rebase before landing

Construct local badge-only notif when notification doesn't have body property

Remove unecessary SQLite initialization from CommHybrid

Rebase before landing

Put SIWE backup secrets persistence to step 1.
Put clearing cached selections to step 2.

Update the comment
Use method to get badge only content for notif.

Add finally statements to set gurd refs to false eventually.

It wasn't easy to introduce new step here. If this solution is not accepted I will just introduce new step that clears cached Selections in the same promise as sqlite persistence and leave avatar upload unchanged.

Introduce two new steps: SQLite data persistence and clearing cached selections

Encrypt with Ethereum Wallet -> Encrypt with Ethereum signature

Remove needsSilentBadgeUpdate function and replace it with inline checks.
Bring back useful comment.

Persist directly to SQLite when forcing user to create backup message signature.

REbase to reflect changes from parent diff

Move siwe secrets persistence and cached selections clearing to registration server call.

If we go back from registration terms screen then siwe backup message creation screen looks like this:

Simulator Screen Shot - iPhone 14 Pro - 2024-04-18 at 09.53.40.png (2×1 px, 144 KB)

Handle existing siwe backup secrets in cached selections.

In D11666#335421, @tomek wrote:

Should we regenerate a wasm file?

Are we able to cache it, such that if the user goes back to before this screen, and then advances to this screen again, the SIWE flow does not need to be re-entered?

Clear all cached selections at once after user becomes logged in. Persist siweBackupSecrets in SQLite beforehand.

Screen with backup icon from MaterialIcons

Simulator Screen Shot - iPhone 14 Pro - 2024-04-16 at 14.11.09.png (2×1 px, 128 KB)

Use backup icon from MaterialIcons

New screen looks like this:

Simulator Screen Shot - iPhone 14 Pro - 2024-04-16 at 13.39.45.png (2×1 px, 135 KB)

Add icon to enchance user experience.

marcin (Marcin)
User

Projects

User Details

Recent Activity
View All

Today

Yesterday

Tue, Apr 23

Mon, Apr 22

Fri, Apr 19

Thu, Apr 18

Wed, Apr 17

Tue, Apr 16

marcin (Marcin)User