App published but users don't not receive messages and I can't download log using export log

[MirianaRebeggianiSacmi]

We have both apps published, Author and User. It seems Author can't send messages correctly but the users never receive them.

Futhermore, I can't download log file:

When this method is executed: GET /api/draftnotifications/scheduledDrafts it gives a 401 error response

Is there something we may have done wrong during the deployment? We have followed the guide.

[gsv022]

Hi @MirianaRebeggianiSacmi , Thank you for raising the query. Could you please verify the graph-app authentication part is correctly done or not. Here is the reference.

• Check supported account type- Myorg
• Check API permissions and Grant Admin Consent is given or not.
• Check URL in authentication and expose an API.

[MirianaRebeggianiSacmi]

Hi Sai Venkat! Yes I've checked it:

[gsv022]

Hi @MirianaRebeggianiSacmi , Please keep the permissions only which are mentioned in the deployment guide.

[MirianaRebeggianiSacmi]

Ok! I've removed "Profile" from permission. Now, I can export results, and I find this error: System.AggregateException: Failed to acquire token for client credentials. (AADSTS700016: Application with identifier '6944d981-0dd6-4957-99d6-eb23e9694ece' was not found in the directory 'd6d49420-f39b-4df7-a1dc-d59a935871db'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant. Trace ID: 3a8dd88d-23b4-4af3-8bd6-6db53a274e00 Correlation ID: e74a6e36-c49d-4435-8939-ffcf7485777a Timestamp: 2024-04-05 09:51:04Z)

But in the Company Communicator doensn't show again the number of recipients: It shows 0 instead of 5

[gsv022]

Hi @MirianaRebeggianiSacmi , We suspect that secrets are incorrectly configured. Here is the procedure for comparison.

• Go to app registration-->open author app registration-->click certificate and secrets-->Grab secret value(not id)

• Go to azure portal-->Go to resource group(Where the deployment has been done)-->Select keyvault from list of resources

• Go to Access Policy--> Click on Create

  

• Select Key, secret and certificate management

  

• Give the Id through which one can view the secrets

  

• 3rd step is optional

• Go for Review+Create

• Then go to Secrets. You will be able to view the secrets. Compare each app secret from keyvault with app registration secret.

[MirianaRebeggianiSacmi]

The secret are corret, I've make a mistake in the config of "users" registration. I've correct it, but still not working, different message of error: Microsoft.Bot.Schema.ErrorResponseException: Operation returned an invalid status code 'Forbidden' at Microsoft.Bot.Connector.Conversations.ReplyToActivityWithHttpMessagesAsync(String conversationId, String activityId, Activity activity, Dictionary2 customHeaders, CancellationToken cancellationToken) at Microsoft.Bot.Connector.ConversationsExtensions.ReplyToActivityAsync(IConversations operations, String conversationId, String activityId, Activity activity, CancellationToken cancellationToken) at Microsoft.Bot.Builder.CloudAdapterBase.SendActivitiesAsync(ITurnContext turnContext, Activity[] activities, CancellationToken cancellationToken) at Microsoft.Bot.Builder.TurnContext.<>c__DisplayClass31_0.<<SendActivitiesAsync>g__SendActivitiesThroughAdapter|1>d.MoveNext() --- End of stack trace from previous location --- at Microsoft.Bot.Builder.TurnContext.SendActivityAsync(IActivity activity, CancellationToken cancellationToken) at Microsoft.Teams.Apps.CompanyCommunicator.Common.Services.Teams.MessageService.<>c__DisplayClass3_1.<<SendMessageAsync>b__1>d.MoveNext() in C:\home\site\repository\Source\CompanyCommunicator.Common\Services\Teams\Messages\MessageService.cs:line 94 --- End of stack trace from previous location --- at Polly.Retry.AsyncRetryEngine.ImplementationAsync[TResult](Func3 action, Context context, CancellationToken cancellationToken, ExceptionPredicates shouldRetryExceptionPredicates, ResultPredicates1 shouldRetryResultPredicates, Func5 onRetryAsync, Int32 permittedRetryCount, IEnumerable1 sleepDurationsEnumerable, Func4 sleepDurationProvider, Boolean continueOnCapturedContext) at Polly.AsyncPolicy.ExecuteAsync[TResult](Func`3 action, Context context, CancellationToken cancellationToken, Boolean continueOnCapturedContext) at Microsoft.Teams.Apps.CompanyCommunicator.Common.Services.Teams.MessageService.<>c__DisplayClass3_0.<b__0>d.MoveNext() in C:\home\site\repository\Source\CompanyCommunicator.Common\Services\Teams\Messages\MessageService.cs:line 94 Now I see the correct number of recepients.

[gsv022]

Please share your mail id so that we can schedule the call and discuss the issue interally

[MirianaRebeggianiSacmi]

My email is miriana.rebeggiani@sacmigroup.com

[gsv022]

We are following the issue internally

[gsv022]

Thanks for joining the call. Here is the summary. During the call it is observed that messages are not getting delivered through any of the sending option. First and second options are giving the error as "Couldn't find any matches"

• As a part of troubleshooting it is noticed that secret were created newly but their new secret identifiers are not updated in the respective places. So we have updated in the respective places.

• In the teams admin center, upload custom app is disabled. So we enabled it.

• All the basic configuration looks fine.

It takes some time for the changes in admin center to reflect in teams. Give 24hrs of time and then try sending messages. Please keep us posted

[microsoft-github-policy-service[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[microsoft-github-policy-service[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.