Closed MartinDawson closed 1 year ago
It's more than just 'npm start'. Based you your screenshots I can see that the dev server was started before 'npm start' was run and so that part was skipped by the start command.
The second image shows that the dev server has started and is ready to serve up content . . . but that won't be needed until you actually start the add-in . . . which you can't until it's loaded. Which narrows it down to the manifest and the version of Office.
Are you able to manually side load the add-in using these instructions? https://docs.microsoft.com/en-us/office/dev/add-ins/outlook/sideload-outlook-add-ins-for-testing?tabs=windows
Prerequisites
Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Expected behavior
TaskPane contoso app is visible and can be loaded in.
Current behavior
You can see it that it looks like npm start is working but the add-in for contoso is not showing in the taskpane.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
Tried with both a react and javascript app. Same issue.
Just
npm start
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.