ReplyToId on mobile clients

[Whity2507]

Steps to reproduce

Hi,
In our Teams Bot we want to update the sign in card after the user has authenticated. So we call turnContext.Activity.ReplyToId in TeamsActivityHandler.OnTeamsSigninVerifyStateAsync to get the activityId for UpdateActivityAsync. When a user logs in from the desktop client, in Activity.ReplyToId we get a correct id like “1732088066556”. But when he logs in from the mobile client Activity.ReplyToId is “0”.
This behavior does not apply to AdaptiveCard, for them Activity.ReplyToId is correct from both desktop and mobile clients.

Expected behavior

turnContext.Activity.ReplyToId is equal for both mobile and desktop clients.

Actual behavior

turnContext.Activity.ReplyToId is always "0" when called from mobile client.

Error details

No response

[sayali-MSFT]

Thank you for your inquiry about your Teams app development issue! To assist you better, could you please provide the following details?
Teams Client Version: What version of the Teams client are you using?
Code Snippets: Relevant code snippets that illustrate the issue.

[Whity2507]

Windows client "About" section:

• Microsoft Teams version 24295.605.3225.8804
• The client version is 49/24102001318

Android client "About" section:

• Version 1416/1.0.0.2024203702/1113
• Calling Version: 2024.40.01.6

Microsoft.Bot framework 4.22.9 (C#)

internal class TeamsActivityHandler : Microsoft.Bot.Builder.Teams.TeamsActivityHandler
{
    protected override Task OnTeamsSigninVerifyStateAsync(ITurnContext<IInvokeActivity> turnContext, CancellationToken cancellationToken)
    {
        var test = turnContext.Activity.ReplyToId; // test = "0" for mobile and test = "1732170698981" for desktop
        ...
    }
    ...
    }

Sign In card:

where _adapter is Microsoft.Bot.Builder.Integration.AspNet.Core.CloudAdapter

[Nivedipa-MSFT]

@Whity2507 - Thanks for the information.

We have logged this as a bug and informed our engineering team. Our engineering team will look into it.

While we cannot guarantee a fix at this stage, we will keep you updated with any progress or changes. Please note that in some cases, the bug may be by design or deprioritized due to platform updates, but we will continue to monitor the bug closely.

We appreciate your patience and understanding as we review the issue.

Thank you again for bringing this to our attention!