OfficeDev / OfficeDev/Office-Addin-Scripts
Proxy issue, created new Outlook Add-In, react, typescript
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 194
- Forks
- 117
- Avg merge
- 1d 32m
- Merged PRs (30d)
- 2
Description
Prerequisites
Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.
- [ x] I am running the latest version of Node and the tools
- [ x] I checked the documentation and found no answer
- [x ] I checked to make sure that this issue has not already been filed
Expected behavior
starting with command:
npx office-addin-usage data off | run start
opens outlook, view Taskpane,
Current behavior
The debug stops with ECONNRESET errors and I cant sideload the Add-In.
The usage data OFF seems not respected by all packages.
Steps to Reproduce
I created new Outlook Add-In, react, typescript.
configured data usage off, set proxy values in .npmrc
Context
Proxy is ZScaler that brings its own Certs and restricts/blocks some connections like a firewall.
- Operating System: Windows
- Node version: 18.20.7
- Office version: Newest
- Tool version:
** office-addin-taskpane-react 0.0.1
Failure Logs
office-addin-taskpane-react@0.0.1 start
office-addin-debugging start manifest.json desktop --app outlook
Debugging is being started...
App type: desktop
Enabled debugging for add-in e3f9823a-d6c8-43a2-bd55-4b2a0c2a1a6d.
Runtime logging is enabled. File: C:\Users\USER\AppData\Local\Temp\2\OfficeAddins.log.txt
Starting the dev server... (webpack serve --mode development)
The dev server is running on port 3000. Process id: 19756
Sideloading the Office Add-in...
Manifest package saved to C:\Users\USER\AppData\Local\Temp\2\manifest.zip
running: npx @microsoft/teamsapp-cli install --file-path "C:\Users\USER\AppData\Local\Temp\2\manifest.zip" --interactive false
--Error sideloading!--
Error: Error: Command failed: npx @microsoft/teamsapp-cli install --file-path "C:\Users\USER\AppData\Local\Temp\2\manifest.zip" --interactive false
ApplicationInsights:CorrelationIdManager [
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
at TCP.callbackTrampoline (node:internal/async_hooks:128:17) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
]
(×) Error: unknown.InternalError: Request failed with status code 400
STDERR:
ApplicationInsights:CorrelationIdManager [
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
at TCP.callbackTrampoline (node:internal/async_hooks:128:17) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
]
(×) Error: unknown.InternalError: Request failed with status code 400
Error: Unable to start debugging.
Error: Unable to sideload the Office Add-in.
Error: Command failed: npx @microsoft/teamsapp-cli install --file-path "C:\Users\USER\AppData\Local\Temp\2\manifest.zip" --interactive false
ApplicationInsights:CorrelationIdManager [
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
at TCP.callbackTrampoline (node:internal/async_hooks:128:17) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
]
(×) Error: unknown.InternalError: Request failed with status code 400
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the office-addin-debugging start entry point and the .npmrc proxy configuration used by the generated React/TypeScript add-in. Trace the npx @microsoft/teamsapp-cli install step and how usage-data-off is passed to the packages. Done means the add-in can be sideloaded behind the stated proxy without ECONNRESET errors and usage reporting remains disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, react, typescript
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100