Transitory data returns incorrect emblemHash

[mikechambers]

https://www.bungie.net/Platform/Destiny2/1/Profile/4611686018429783292/?components=1000

Transitory data is returning incorrect emblemHash for all players (2166136261).

This was during an Iron Banner match.

                    {
                        "membershipId": "4611686018467477798",
                        "emblemHash": 2166136261,
                        "displayName": "SpartnMarine816",
                        "status": 3
                    },

(complete output included below)

Note that all emblemHash's return 2166136261, which does not appear to be a valid emblem hash.

Note, may be be related to: https://github.com/Bungie-net/api/issues/910

{
    "Response": {
        "profileTransitoryData": {
            "data": {
                "partyMembers": [
                    {
                        "membershipId": "4611686018429783292",
                        "emblemHash": 2166136261,
                        "displayName": "mesh",
                        "status": 11
                    },
                    {
                        "membershipId": "4611686018493042576",
                        "emblemHash": 2166136261,
                        "displayName": "Elsexyboy",
                        "status": 3
                    },
                    {
                        "membershipId": "4611686018484407348",
                        "emblemHash": 2166136261,
                        "displayName": "Yuno",
                        "status": 3
                    },
                    {
                        "membershipId": "4611686018488582013",
                        "emblemHash": 2166136261,
                        "displayName": "Tana",
                        "status": 3
                    },
                    {
                        "membershipId": "4611686018467477798",
                        "emblemHash": 2166136261,
                        "displayName": "SpartnMarine816",
                        "status": 3
                    },
                    {
                        "membershipId": "4611686018495544264",
                        "emblemHash": 2166136261,
                        "displayName": "Bean",
                        "status": 3
                    }
                ],
                "currentActivity": {
                    "startTime": "2020-09-13T01:13:22Z",
                    "endTime": "2020-09-13T01:24:20Z",
                    "score": 2.0,
                    "highestOpposingFactionScore": 8.0,
                    "numberOfOpponents": 6,
                    "numberOfPlayers": 12
                },
                "joinability": {
                    "openSlots": 0,
                    "privacySetting": 1,
                    "closedReasons": 0
                },
                "tracking": [
                    {}
                ],
                "lastOrbitedDestinationHash": 1504512062
            },
            "privacy": 1
        }
    },
    "ErrorCode": 1,
    "ThrottleSeconds": 0,
    "ErrorStatus": "Success",
    "Message": "Ok",
    "MessageData": {}
}

[jshaffstall-bng]

Interesting! That value of 2166136261 represents an 'invalid hash' for any kind of Destiny content, so it's possible that the emblem data just isn't available to deliver via this API.

I've filed TFS 957681 to investigate.