Change Details

This diff introduces handling of the `newNotifyToken` in `Get` stream request. When the device has an invalid or expired notification token we are requesting a new token from the client (ref to D5207). The client gets back with the new token in `Get` stream request when starts listening for new messages (getting messages) from the Tunnelbroker. This is a part of the stack. This approach was used keeping in mind the transition to the bidirectional stream soon. Related Linear task: [[ https://linear.app/comm/issue/ENG-1782/generate-notice-for-client-for-invalid-device-tokens-in-tunnelbroker | ENG-1782 ]] and [[ https://linear.app/comm/issue/ENG-1816/update-tunnelbroker-api-to-support-sending-notices-to-clients-for | ENG-1816 ]]

TBDhis diff introduces handling of the `newNotifyToken` in `Get` stream request. When the device has an invalid or expired notification token we are requesting a new token from the client (ref to D5207). The client gets back with the new token in `Get` stream request when starts listening for new messages (getting messages) from the Tunnelbroker. This is a part of the stack. This approach was used keeping in mind the transition to the bidirectional stream soon. Related Linear task: [[ https://linear.app/comm/issue/ENG-1782/generate-notice-for-client-for-invalid-device-tokens-in-tunnelbroker | ENG-1782 ]] and [[ https://linear.app/comm/issue/ENG-1816/update-tunnelbroker-api-to-support-sending-notices-to-clients-for | ENG-1816 ]]