npm run start failing on newly created project

[casebrophy]

Describe the bug
Getting a 404 error when trying to sideload and outlook add-in.

-- relevant logs ---

sendTelemetryEvent ===> ttk-mos-api-start, properties: {"bin-name":"teamsapp","url":"<https:--titles.prod.mos.microsoft.com-dev-v1-users-packages-acquisitions-url>","method":"post","params":"","correlation-id":"9bc60c56-1592-445a-8d93-bce83d244e61","run-from":"Other"}
sendTelemetryEvent ===> ttk-mos-api, properties: {"bin-name":"teamsapp","url":"<titles.prod.mos.microsoft.com-dev-v1-users-packages-acquisitions-url>","method":"POST","params":"","success":"yes","status-code":"200","correlation-id":"9bc60c56-1592-445a-8d93-bce83d244e61","run-from":"Other"}Acquiring package with statusId: 1f52feb9-a52e-45a3-960a-2474a5f19af9 ...
sendTelemetryEvent ===> ttk-mos-api-start, properties: {"bin-name":"teamsapp","url":"<https:--titles.prod.mos.microsoft.com-dev-v1-users-packages-status-1f52feb9-a52e-45a3-960a-2474a5f19af9-url>","method":"get","params":"","correlation-id":"9bc60c56-1592-445a-8d93-bce83d244e61","run-from":"Other"}
sendTelemetryErrorEvent ===> ttk-mos-api, properties: {"bin-name":"teamsapp","url":"<titles.prod.mos.microsoft.com-dev-v1-users-packages-status-1f52feb9-a52e-45a3-960a-2474a5f19af9-url>","method":"GET","params":"","success":"no","err-message":"Request failed with status code 404 (tracingId: 00-d6a151ca42aae0b305fdf7aa00219828-3a6809a5643c7f33-00) :  ","status-code":"404","mos-trace-id":"00-d6a151ca42aae0b305fdf7aa00219828-3a6809a5643c7f33-00","mos-api-path":"titles.prod.mos.microsoft.com/dev/v1/users/packages/status/1f52feb9-a52e-45a3-960a-2474a5f19af9","correlation-id":"9bc60c56-1592-445a-8d93-bce83d244e61","run-from":"Other"}
sendTelemetryErrorEvent ===> m365-sideloading, properties: {"bin-name":"teamsapp","command-name":"teamsapp install","component":"cli","run-from":"Other","command-debug":"true","command-verbose":"true","command-help":"undefined","command-interactive":"false","command-version":"undefined","success":"no","error-code":"m365.InternalError","error-type":"user","err-message":"Request failed with status code 404 <REDACTED:secret>: <REDACTED:secret> :  ","err-stack":"assembleError | PackageService.sideLoading | process.processTicksAndRejections | async PackageService.<anonymous>","error-name":"InternalError","error-component":"PackageService","error-stage":"","error-method":"getTitleServiceUrl","error-source":"M365","error-inner-code":"ERR_BAD_REQUEST","error-cat":"internal|ERR_BAD_REQUEST","error-cat1":"internal","error-cat2":"ERR_BAD_REQUEST","correlation-id":"9bc60c56-1592-445a-8d93-bce83d244e61"}

---

Steps to reproduce the behavior:

1. run yo office > create add-in for outlook > unified manifest
2. run npm run start
3. login to Microsoft when prompted
4. 404 error is returned

Expected behavior
Add-in should be sideloaded

VS Code Extension Information (please complete the following information):

• OS: Windows 10
• Version 10.0.19045

Additional context

Something else of note is that this was working fine for me the other day, and just stopped working this morning. The info on what is actually going wrong is so limited that I can't think of any further steps to take to resolve this. My add-in is still uploaded, but I'm not sure what repercussions this error may have.

[microsoft-github-policy-service]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

[jayzhang]

@casebrophy In your reproduce step, there is no Teams Toolkit involved. Can you describe it more details? Or maybe you should submit the issue in : https://github.com/OfficeDev/generator-office

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[microsoft-github-policy-service]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible.