Signature doesn't set for New emails, replies, or forwards.

[lhuisenga5]

Note: This repo is only for questions related to its samples. If you have questions about how to use office.js or the Office developer platform, please post your question on https://stackoverflow.com. Tag your question with office-js or outlook-web-addins

Question

Ask your question here.

Is there a known issue where it doesn't auto assign the signature for new emails, replies, or forwards? I selected the overwrite signature button, and it did remove my current one but the sample one never populates when I go to new email or reply.

I tested on New Outlook and web Outlook. I am testing it with npm running locally, and I am using the unified manifest one. I copied the files over like that sample says, and the preview does populate from the button on the task pane but it doesn't stay when I go to new email or reply. Any help would be appreciated.

[AlexJerabek]

Hi @lhuisenga5,

I'm sorry to hear you're having problems with this feature. There are some known issues involving set signature but this sounds like a different issue. Since this appears to be a product bug, I'm going to transfer the issue to the office-js repo, where such issues are triaged by the product team.

(Just to be clear, the sample you're working with is this one, right?)

[JuaneloJuanelo]

This issue is not actionable as described here. We need more information.

@lhuisenga5 can you please fill the required information? including the link for the sample. Here is a template we use for this. thanks so much.

Provide required information needed to triage your issue

Your Environment

• Platform [PC desktop, Mac, iOS, Office on the web]: ______
• Host [Excel, Word, PowerPoint, etc.]: ______
• Office version number: ______
• Operating System: ______
• Browser (if using Office on the web): ______

Expected behavior

Current behavior

Steps to reproduce

1. ---

2. ---

3. ---

Link to live example(s)

1. ---

2. ---

3. ---

Provide additional details

1. ---

2. ---

3. ---

Context

Useful logs

• Console errors
• Screenshots
• Test file (if only happens on a particular file)

Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.