search

OfficeDev / office-js

A repo and NPM package for Office.js, corresponding to a copy of what gets published to the official "evergreen" Office.js CDN, at https://appsforoffice.microsoft.com/lib/1/hosted/office.js.
https://learn.microsoft.com/javascript/api/overview
Other
678 stars 95 forks source link

Add-ins don't work in Excel Online and Mac #4733

Closed irynakaban closed 1 month ago

irynakaban commented 3 months ago

Provide required information needed to triage your issue

All add-ins doesn't work in Excel. Receive or endless loading, or error.

Your Environment

Expected behavior

Add-ins work correctly.

Current behavior

Receive or endless loading, or error.

Steps to reproduce

  1. Open add-in store from excel.
  2. Install ScriptLab from add-ins store.

Link to live example(s)

  1. Link to video on google drive
microsoft-github-policy-service[bot] commented 3 months ago

Thank you for letting us know about this issue. We will take a look shortly. Thanks.

gmichaud commented 3 months ago

Same here -- https://appsforoffice.microsoft.com/lib/1/hosted/office.js is not loading from Canada (but is apparently fine from Portugal, according to other team members)

Problem is affecting other Office apps as well.

gmichaud commented 3 months ago

I tested with a service that loads the page from multiple locations. Results can be seen here: https://semonto.com/tools/website-reachability-check?test=a60f4a2e6c573f1

Screenshot 2024-07-30 at 9 32 37 AM
alexm-plutoflume commented 3 months ago

We are also having reports of our Outlook ItemSend Add-in hanging when trying to reach office.js

MSFT has reported service issues with M365, likely related?

https://x.com/MSFT365Status/status/1818267438435147865

Issue ID MO842351 in the admin center

wh1t3cAt1k commented 3 months ago

The issue seems to have been resolved by now.

https://semonto.com/tools/website-reachability-check?test=2d7e174246175b34292aff94725551bc6a80

atsopuronen commented 3 months ago

Same here with our Outlook add-in, multiple reports from our customers.

hdwatts commented 3 months ago

Issue was resolved but is now occurring again.

hdwatts commented 3 months ago

Looks like the issue has resolved itself again.

@shanshanzheng-dev What steps can we take to mitigate this issue should the CDN go down again? Is it safe for us to self host the office.js file as a backup?

shanshanzheng-dev commented 3 months ago

Thanks for reporting this issue. Yes, looks like the issue has resolved again. We've connected with our partner team to consider on future for a fallback mechanism and we'll also keep monitoring if it occur again. Thanks.

bchen-hs-eng commented 2 months ago

@shanshanzheng-dev We'd like to follow up on the fallback mechanism effort. Is this something your and the partner team will handle internally so it is transparent to us, or do we need to manually configure the fallback when loading the evergreen OfficeJS script?

shanshanzheng-dev commented 2 months ago

Thanks @bchen-hs-eng. Hi @gergzk We think it makes sense if customer manually configure the fallback when loading the evergreen OfficeJS script. Not sure if you have some good insights about the fallback mechanism, seem office.js deployment/CDN is out of our control.

gergzk commented 1 month ago

Per https://semonto.com/tools/website-reachability-check?test=2d7e174246175b34292aff94725551bc6a80 this is fine now, so I'll close with comments.

Developers should not bundle office.js with their add-in.

If in the future this is observed again, a network trace of attempting to get the office.js file would be most useful, as well as a session id (eg: File -> Info, copy/paste session id)