presenceChanged callback not getting called on Android Teams app. about live-share-sdk

[huntj88]

@mscherotter We are unable to replicate the presenceChanged callback not being called on android, can you tell us a little more about your scenario?

[mscherotter]

I have built a scenario based on this sample https://github.com/davrous/metaverseliveshare
On android, this call
await _presence.update(data, PresenceState.online);

throws an exception "The local user doesn't meet the app requirements to send a message for this app." Does Teams on Android need any additional permissions? the code works just fine running in Edge or the Teams desktop app on Windows 11.

This is the container schema that I am using:

const containerSchema = {
    initialObjects: {
        appState: LiveState<IShowState>,
        presence: LivePresence<IAvatarData>,
        notifications: LiveEvent,
        liveCanvas: LiveCanvas
    },
};

This is the permissions section from my manifest:

"authorization": {
        "permissions": {
            "resourceSpecific": [
                {
                    "name": "MeetingStage.Write.Chat",
                    "type": "Delegated"
                },
                {
                    "name": "ChannelMeeting.ReadBasic.Group",
                    "type": "Application"
                },
                {
                    "name": "ChannelMeetingStage.Write.Group",
                    "type": "Delegated"
                },
                {
                    "name": "LiveShareSession.ReadWrite.Group",
                    "type": "Delegated"
                },
                {
                    "name": "LiveShareSession.ReadWrite.Chat",
                    "type": "Delegated"
                },
                {
                    "name": "MeetingParticipantReaction.Read.User",
                    "type": "Delegated"
                }
            ]
        }
    }

Michael

[ryanbliss]

Another partner has reported this same issue. Our mobile team is investigating as part of their next sprint.

[huntj88]

@mscherotter Are you specifying allowed roles in the initialize function for presence? I see that you are not in the sample you linked.

Are you able to replicate this issue on iOS?

[ryanbliss]

We found the issue. There is an Android client issue that we were finally able to repro and pinpoint. The teams-js response Android was sending for one of our APIs is formatted incorrectly in some cases. We will work on an update to the Android client, but fortunately all of the data needed is in the response. A polyfill that we tested solved the issue, so we will fix this in the next update!

[ryanbliss]

This has been published as of version 1.0.2, or for turbo/react packages, 1.0.2-preview.1. Thanks for your patience!

[mscherotter]

I am seeing this issue and I am not using the turbo/react package.

[mscherotter]

@huntj88 I see the issue whether I pass the allowed roles or not. I have tried both scenarion.

[huntj88]

It looks like obfuscation is causing the keys of the clientInfo object to change between different android builds