-
Notifications
You must be signed in to change notification settings - Fork 120
Office.context.urls.javascriptRuntimeUrl Causes Add-in Timeout in Outlook Version 2602 (Build 19725.20190) on Current Channel #6596
Description
Environment
| Field | Details |
|---|---|
| Platform | PC desktop |
| Host | Outlook |
| Office version | Version 2602 (Build 19725.20190) |
| Operating System | Windows 11 |
Expected Behavior
Accessing Office.context.urls.javascriptRuntimeUrl should have no side effects. The add-in should continue to function normally, as this is a standard read-only property of the office.js API — its mere reference should not affect add-in performance or stability.
Current Behavior
The add-in times out immediately upon introduction of the single line Office.context.urls.javascriptRuntimeUrl, with no other code changes made.
This regression does not reproduce on:
- Version 2508 (Build 19127.20264)
- Monthly Enterprise Channel Version 2602 (Build 19725.20170) — same major version, different build number
This strongly suggests the issue was introduced in a specific update within the Current Channel.
Steps to Reproduce
- Clone the official Microsoft spam-reporting sample:
https://github.com/OfficeDev/Office-Add-in-samples/blob/main/Samples/outlook-spam-reporting - Run the add-in as-is to confirm it works correctly out of the box.
- Add the following single line anywhere in the add-in code:
Office.context.urls.javascriptRuntimeUrl- Reload and run the add-in in Outlook Version 2602 (Build 19725.20190).
- Observe that the add-in times out immediately.
Link to Live Example(s)
- Base sample: https://github.com/OfficeDev/Office-Add-in-samples/blob/main/Samples/outlook-spam-reporting
Context
This issue is blocking development of an Outlook spam-reporting add-in that relies on Office.context.urls.javascriptRuntimeUrl as part of its runtime logic. Since Office.context.urls is owned and maintained by Microsoft as part of the office.js library, we believe this is an unintended regression introduced in Build 19725.20190. We are requesting confirmation of whether this is a known issue and whether any workaround is available in the meantime.
Useful Logs
- Screenshots
