aximut

Thanks! That was it. Now I see the code being fully executed. ``` D SyncKeysRequest: STARTING GRPC REQUEST PHASE 5 D SyncKeysRequest: STARTING GRPC REQUEST PHASE 6 D SyncKeysRequest: STARTING...

Ok, then I'll try with the new version soon.

That would explain why the request went through on my device but I'm still facing the errors

> * We need to complete the cryptauth flow by sending an EnrollKeys query, which constitutes the second half of the flow (as per https://github.com/chromium/chromium/blob/1de4545b5a22b1d290043b3bddd96a4cb3c730dd/chromeos/ash/services/device_sync/proto/cryptauth_enrollment.proto#L5-L17). Ok, this matches with what...

> I have implemented the EnrollKeys step. @aximut If you want to try again, unlocking the device should now work with the latest changes on our `basic-workspace` branch. @fynngodau You...

Does anyone know where to look into? Is this just an argument missing (somewhere we need to pass something like `ScreenLock=enabled`) or is there some trusted signatures required that our...

Since nobody answered my questions above, I spent some time to see what is missing. Same as for #1726. It is EXACTLY 2 requests. The original GMS app also gets...

Thanks for sharing and putting everything in a useful file! That is very interesting that the protobufs are part of the chromium repo. I did not find any references when...

> It's not really as complex, many of the intimidating fields can be removed and the `EnrollKeys` step is optional for us. That is good news. Didn't expect Google to...

Thanks a lot for making this happen @fynngodau ! Will test this as soon as possible.