Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug len(None) communication extension inline attachments #8123

Open
manuelmazzuola opened this issue Oct 10, 2024 · 4 comments
Open

Bug len(None) communication extension inline attachments #8123

manuelmazzuola opened this issue Oct 10, 2024 · 4 comments
Labels
Auto-Assign Auto assign by bot Communication Label for AzureCommunicationServices customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@manuelmazzuola
Copy link

manuelmazzuola commented Oct 10, 2024

Describe the bug

With the new version 1.11.0 and the introduction of inline attachments for the azure communication extension,
a bug raises with a len of None object error when not setting the inline attachments.

Thanks.

Related command

az communication email send

Errors

object of type 'NoneType' has no len()

Issue script & Debug output

az communication email send \
        --connection-string "${AZURE_COMMUNICATION_SERVICE_ENDPOINT}" \
        --sender "DoNotReply@${AZURE_FROM_SENDER_DOMAIN}" \
        --to "${to_email}" \
        --subject "TEST" \
        --text "See the attachment." \
        --attachments ${filename} \
        --attachment-types plain/text

Expected behavior

Should work.

Environment Summary

azure-cli 2.64
azure communication extension 1.11.0

Additional context

Using azure communication extension 1.10.0 everything work as expected..

@manuelmazzuola manuelmazzuola added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Oct 10, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. Auto-Assign Auto assign by bot labels Oct 10, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Oct 10, 2024

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added Communication Label for AzureCommunicationServices Service Attention This issue is responsible by Azure service team. labels Oct 10, 2024
@yonzhan yonzhan removed the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Oct 10, 2024
@ealmuneyeer
Copy link
Member

ealmuneyeer commented Oct 14, 2024

@manuelmazzuola , thank you for reporting this, and sorry for the inconvenience. I was able to reproduce it locally. As a workaround, I downgraded the communication extension to version 1.10.0, which allowed me to send the email successfully as you mentioned.

Here are the useful commands for everyone else:
To remove the extension:
az extension remove --name communication

To install communication extension v1.10.0:
az extension add --name communication --version 1.10.0

@ealmuneyeer
Copy link
Member

@manuelmazzuola , a new communication extension version 1.11.1 has been released and it includes the fix.

@manuelmazzuola
Copy link
Author

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot Communication Label for AzureCommunicationServices customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants