Page MenuHomePhabricator

[lib] handle `BadDeviceToken` message
ClosedPublic

Authored by kamil on Jul 29 2024, 2:56 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Dec 19, 10:39 AM
Unknown Object (File)
Thu, Dec 19, 10:39 AM
Unknown Object (File)
Thu, Dec 19, 10:39 AM
Unknown Object (File)
Thu, Dec 19, 10:39 AM
Unknown Object (File)
Tue, Nov 26, 3:25 AM
Unknown Object (File)
Nov 22 2024, 1:24 PM
Unknown Object (File)
Nov 9 2024, 11:36 PM
Unknown Object (File)
Nov 9 2024, 4:15 PM
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
Lint
Lint Not Applicable
Unit
Tests Not Applicable

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 ↗(On Diff #42864)

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

We have a convention that this name should end in ActionType

lib/actions/tunnelbroker-actions.js
9

thanks for catching: D12968