0.3.7 Update

[firebolt55439]

Just opening a discussion for any protobuf-related changes due to the new 0.3.7 (1.7.0 iOS) update. It appears unknown6 structure has changed (again), as well as some initial requests made on authentication.

[apavlinovic]

Can anyone verify if the egg distance tracking is recorded more frequently in 0.37.0?

[Kermel]

Has anyone also found out what is the current value for unknown25 ?

[Grover-c13]

the encryption for the Signature/SignalLog/U6 has changed, so no.

[gise88]

is there someone who is already working on it?

[langit7]

Just got force update to 0.39. botting is dead now

[vankxr]

Signature changed?

I am running my own API and Bot with this protos in nodejs and its working normally.

EDIT: Stopped working atm...

[vankxr]

I've got this from a 0.39.1 initial authentication:

1: 1
2: 2
3: 1
4 {
  1: 3
}

The current protos don't have any fourth field at the response envelope, so... I don't know where to go next :|

[Grover-c13]

Thats just the safteynet auth envelope sent on android, normal requwst envelopes resume after this one

Sent from my Samsung GALAXY S5

-------- Original message -------- From: João Silva notifications@github.com Date: 9/10/2016 10:00 PM (GMT+08:00) To: AeonLucid/POGOProtos POGOProtos@noreply.github.com Cc: Grover-c13 Grover.c13@gmail.com, Comment comment@noreply.github.com Subject: Re: [AeonLucid/POGOProtos] 0.3.7 Update (#233)

I've got this from a 0.39.1 initial authentication:

1: 1 2: 2 3: 1 4 { 1: 3 }

The current protos don't have any fourth field at the response envelope, so... I don't know where to go next :|

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/AeonLucid/POGOProtos","title":"AeonLucid/POGOProtos","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/AeonLucid/POGOProtos"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Vankxr in #233: I've got this from a 0.39.1 initial authentication:\r\n\r\n\r\n1: 1\r\n2: 2\r\n3: 1\r\n4 {\r\n 1: 3\r\n}\r\n\r\n\r\nThe current protos don't have any fourth field at the response envelope, so... I don't know where to go next :|"}],"action":{"name":"View Issue","url":"https://github.com/AeonLucid/POGOProtos/issues/233#issuecomment-252488019"}}}

[vankxr]

@Grover-c13 I've also got this from the request, and this doesn't seem to be matching with the current RequestEnvelope proto

1: 1
2: 2 //What is this second field?
3: 1
4 {
  1 { //Repeated (not as the current protos)
    1: "google"
  }
}

So i editted the protos, like this:

message NewResponseEnvelope {
    int32 status_code = 1;
    int32 unk2 = 2;
    int32 unk3 = 3;
    repeated unk4msg unk4 = 4;

    message unk4msg {
        int32 auth_status = 1;
    }
}

message NewRequestEnvelope {
    int32 status_code = 1;
    int32 unk2 = 2;
    int32 unk3 = 3; //Guess it's not request ID...
    repeated unk4msg unk4 = 4;

    message unk4msg {
        repeated AuthInfo auth_info = 1;

        message AuthInfo {
            string provider = 1;
        }
    }
}

[vankxr]

Does anyone know how to bypass those envelopes? I am making a custom server and I would like not having those :/

[AeonLucid]

Closing this issue, let me know if this is still relevant.