-
Notifications
You must be signed in to change notification settings - Fork 802
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
Edit the Existing mail #799
Comments
Hi @SindhuChenna, Thanks for reporting this. Could you please share which version of Outlook you're using (web, Mac, Windows Classic, New Outlook for Windows)? Also, just to clarify, are you using the GitHub hosted version (manifest.xml), or are you running the web server on localhost (manifest-localhost.xml? |
Hi, |
Thank you for the reply. When you say you've "copied manifest,xml and html files", could you please elaborate? If you're building the project and running it locally, you'll need to copy everything from the repo. If you're sideloading the GitHub hosted version, you should only need the manifest. Also, I reran the sample and could not reproduce those errors. |
@exextoc, could you please take a look? |
Hi @SindhuChenna, to run the sample from localhost, you need to put the localhost.key and .crt files in the |
This issue has been automatically marked as stale because it is marked as needing 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. Thank you for your interest in Office Add-ins! |
This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue. |
https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/hello-world/outlook-hello-world
Describe the bug
On click of button getting error
Uncaught TypeError: Office.context.mailbox.item.body.setAsync is not a function
at HTMLButtonElement.sayHello
To Reproduce
Steps to reproduce the behavior:
at HTMLButtonElement.sayHello
Expected behavior
Display the required message in the email body
Screenshots
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: