Incense Encounters Don't Work about pogoprotos HOT 9 CLOSED

encounter_id for the encounter message needs to be int64...even though the encounter_id on the incensePokemon message is fixed64. I had the same issue, but I got it working by reverting the encounter message back to int64.

from pogoprotos.

@prorook thanks, I will give it a try. What's the correct way to transform a fixed64 to an int64 in python? I ask cause I get errors thrown if I don't do a conversion (perhaps because I use an older version of protobuf).

from pogoprotos.

Thank you, got it working after fixing the GetIncensePokemonResponse to PokemonId enum, rather than int32

from pogoprotos.

Actually, it still fails at times...

for large encounter_id type-casting to python's int() doesn't work at times.

I just got two encounter_ids (1 worked, 1 didn't)
WORKED: 6180230722423979422
FAILED: 10965396974330624794 <-- this is bigger than int64 and smaller than uint64

from pogoprotos.

How are incense encounters caught without a spawn_point_id?

from pogoprotos.

@RyanHope they are not, you get one from GetIncencePokemon response.

from pogoprotos.

Not according to https://github.com/AeonLucid/POGOProtos/blob/master/src/POGOProtos/Networking/Responses/GetIncensePokemonResponse.proto

from pogoprotos.

@RyanHope it's called "encounter_location"

from pogoprotos.

This is about to be fixed with LureInfo being replaced. Spawn point ids are actually fort ids in this case.

from pogoprotos.