OfficeDev / microsoft-teams-apps-company-communicator

Company Communicator app template
MIT License
328 stars 400 forks source link

"Something went wrong. Please try again." when downloading exported results #1541

Closed EMEAWebEnvironmentsTeam closed 1 week ago

EMEAWebEnvironmentsTeam commented 3 weeks ago

Hello,

We are having an issue since deployment when trying to export detailed results, the file becomes available to download, but at the stage it says "GTS Incident Alerts (UAT) A needs permission to upload this file to your OneDrive", clicking the Allow button gives the error message "Something went wrong. Please try again."

Screenshot 2024-08-20 112410

In Failures, it comes back with error code 409 "Azure.RequestFailedException: The specified container already exists." under BlobContainerClient.Create

In BlobClient.Upload, the command (replaced data with x) https://x.blob.core.windows.net/exportdatablobs/ExportData_x.zip appears, but when browsing to this page, it gives the error "Public access is not permitted on this storage account."

However, in the storage account Networking, public access is enabled:

image

Any suggestions for what we can check would be appreciated!

peddivyshnavi commented 3 weeks ago

Hi @EMEAWebEnvironmentsTeam Thanks for reaching out to us. Could you Please confirm us with the following.

EMEAWebEnvironmentsTeam commented 3 weeks ago

Thanks for your response.

We appear to have the correct api permissions set up: image

As for sending 4 different ways, the first two options give a 'we couldn't find any matching...' error

image image

Sending to all users we assume works, but we have a lot of different users and so don't want to confuse them with a message.

image

The last option is working and sends messages successfully

image
peddivyshnavi commented 3 weeks ago

Hi @EMEAWebEnvironmentsTeam As for sending 4 different ways, the first two options give a 'we couldn't find any matching...' error: For making teams visible we need to add User app from manage apps so that teams will be visible while sending message via first two sending options. We appear to have the correct api permissions set up: could you please go through deployement guide whether Set-up Authentication added correctly or not. and please share the error the supporting screenshot of error from application insights resource from the deployed resource group. Go to resource group where CC app is deployed --> Go to Application insight type resource

peddivyshnavi commented 3 weeks ago

Hi @EMEAWebEnvironmentsTeam Could you please update us on the status of the issue?

peddivyshnavi commented 2 weeks ago

@EMEAWebEnvironmentsTeam Could you please update us on the status of the issue? if issue is resolved please feel free to mark ticket as complete

peddivyshnavi commented 1 week ago

@EMEAWebEnvironmentsTeam Please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at the moment and no response is received, we will close out the issue in 2 business days.

peddivyshnavi commented 1 week ago

Marking This ticket as closed