[native] fix not starting backup handler when performing migration to new flow
AbandonedPublic
Actions

Authored by kamil on Jan 16 2025, 2:34 PM.

Details

Reviewers

bartek
tomek

Summary

ENG-10094.

This is an actual fix to the issue, we might want to migrate on a non-primary device. In that case, we need to additionally run a backup handler.

Depends on D14214

Test Plan

Tested if issue from the ENG-10094 - Identity is called but migration fails because of ENG-10101.

Diff Detail

Repository

rCOMM Comm

Branch

publish-flow-fixes

Lint

No Lint Coverage

Unit

No Test Coverage

Event Timeline

kamil created this revision.Jan 16 2025, 2:34 PM

kamil held this revision as a draft.

Herald added a subscriber: ashoat. · View Herald TranscriptJan 16 2025, 2:34 PM

kamil retitled this revision from [native] fix not staring backup handler when performing migration to new flow to [native] fix not starting backup handler when performing migration to new flow.Jan 16 2025, 2:36 PM

kamil added a child revision: D14216: [native] handle errors when running migration to new flow.Jan 16 2025, 2:40 PM

kamil published this revision for review.Jan 16 2025, 2:48 PM

kamil edited the summary of this revision. (Show Details)

Harbormaster completed remote builds in B33256: Diff 46700.Jan 16 2025, 2:53 PM

tomek accepted this revision.Jan 17 2025, 11:38 AM

This revision is now accepted and ready to land.Jan 17 2025, 11:38 AM

kamil planned changes to this revision.Jan 20 2025, 11:22 AM

kamil removed a child revision: D14216: [native] handle errors when running migration to new flow.Jan 20 2025, 11:43 AM

kamil abandoned this revision.Jan 21 2025, 1:49 PM

Revision Contents
Changeset List

Path

Size

native/

backup/

backup-handler.js

54 lines

Diff 46700

View Options

native/backup/backup-handler.js

[native] fix not starting backup handler when performing migration to new flowAbandonedPublicActions