We’ve shipped fixes for a few scenarios that can cause this in 1902 but know there are some scenarios left.
May we ask anyone still experiencing it on 1902 to gather verbose logs from the client and send a frown so we can troubleshoot additional scenarios that cause the error.