Page MenuHomePhabricator

[lib] handle `BadDeviceToken` message
ClosedPublic

Authored by kamil on Jul 29 2024, 2:56 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Sep 10, 5:16 PM
Unknown Object (File)
Sun, Sep 8, 2:20 AM
Unknown Object (File)
Sat, Sep 7, 7:15 AM
Unknown Object (File)
Tue, Sep 3, 1:39 PM
Unknown Object (File)
Sun, Sep 1, 4:45 AM
Unknown Object (File)
Sun, Sep 1, 4:45 AM
Unknown Object (File)
Sun, Sep 1, 4:44 AM
Unknown Object (File)
Sun, Sep 1, 4:43 AM
Subscribers

Details

Summary

ENG-8498.

Updating state after receiving message from TB.

Depends on D12911

Test Plan

Repeat test plan from D12911

Diff Detail

Repository
rCOMM Comm
Branch
publish-device-token
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil edited the test plan for this revision. (Show Details)
kamil published this revision for review.Jul 29 2024, 6:42 AM
kamil added a reviewer: tomek.
kamil added inline comments.
lib/reducers/tunnelbroker-device-token-reducer.js
37–38

We set tunnelbrokerToken to null because when receiving BAD_DEVICE_TOKEN Tunnelbroker is no longer trying to use that device token - so we can assume Tunnelbroker doesn't have any token.
Additionally, this makes TunnelbrokerDeviceTokenHandler to upload token even if the same token was retrieved by native API (I think there is a really low chance for this, but still worth handling).

This revision is now accepted and ready to land.Jul 30 2024, 2:22 AM
This revision was automatically updated to reflect the committed changes.
lib/actions/tunnelbroker-actions.js
9 ↗(On Diff #43010)

We have a convention that this name should end in ActionType

lib/actions/tunnelbroker-actions.js
9 ↗(On Diff #43010)

thanks for catching: D12968