iOS activity reporting is incorrect

[robertmclaws]

The logic in ActivityStatusIOS is all wonky. It reports that you're standing still and moving at the same time. Windows reports speed in m/s, so the number being used are unrealistic. And there are bounding logic flaws for the Walking calculation.

Could be related to #1245, #1460, etc.

[EpikYummeh]

I wonder if this mix-up might have been a ban trigger. Good find.

[WallyCZ]

The biggest problem is, that this structure probably does not match iOS Activity API (see newer protos, they reverted it to unknown). I have some dumps, where stationary flag is always true and others values are weird. I don't own any iCrap, so i can't check it.

PS: Please don't try fix anything without real dumps - situation could be even worst than before

[robertmclaws]

AFAIK that team started over and reverted everything back to unknown. I don't think that means they don't know what it is. I think they want to re-discover everything. Was going to ask them tomorrow.

[jakubsuchybio]

I was digging into possible combinations and:
Having Automotive, Running or Walking true results in 0map items.
Only this is working for every speed use for me:

private class ActivityStatusIOS : IActivityStatus
        {
            public bool Automotive => false;
            public bool Cycling => LocationServiceHelper.Instance.Geoposition?.Coordinate?.Speed > 3.33333;
            public bool Running => false;
            public bool Stationary => LocationServiceHelper.Instance.Geoposition?.Coordinate?.Speed < 0.2;
            public bool Tilting => Utilities.Rand.NextBoolean();
            public bool Walking => false;
        }

[robertmclaws]

I have a sneaky feeling that this proto has incorrect property names.

[jakubsuchybio]

Yeah, because this doesn't make any sense at all.
The only thing coming to my mind and having Automotive, Running or Walking to be false is, that you shouldn't use Pokemon GO when you have navigation ON for either car,run,walk.