"Cannot initialize Addon without a ResourceScope" error when opening file from Teams in SharePoint File Handler App

Question

The error "Cannot initialize Addon without a ResourceScope" has started appearing a few days ago in a SharePoint Online tenant when trying to open a file from Teams in a SharePoint file handler app.

In Chrome DevTools we can see that error in Console, originating from spofilehandlerproxy.js. The page remains blank.

In a different tenant, opening the files from Teams still works.

We noticed that on the tenant where the error appears there is a newer version of the spofilehandlerproxy.js file: [https://res-1.cdn.office.net/files/odsp-web-prod_2024-05-03.004/spofilehandlerproxy/spofilehandlerproxy.js](https://res-1.cdn.office.net/files/odsp-web-prod_2024-05-03.004/spofilehandlerproxy/spofilehandlerproxy.js "res-1.cdn.office.net") On the tenant where it still works, there is an older version: [https://res-1.cdn.office.net/files/odsp-web-prod_2024-04-26.006/spofilehandlerproxy/spofilehandlerproxy.js](https://res-1.cdn.office.net/files/odsp-web-prod_2024-04-26.006/spofilehandlerproxy/spofilehandlerproxy.js "res-1.cdn.office.net")

The older file doesn't throw that error. It is only thrown in the new file.

Any idea what may be causing it and how to fix it? Thank you.

Answer 1

A regression was identified in the service that is impacting file handlers. A fix is now rolling out across the service and should be fully in production by June 24.

Answer 2

Hi,

I haven't encountered this issue.

The original "Cannot initialize Addon without a ResourceScope" error I posted, was fixed by the update roll out Patrick Rodgers mentioned above.

Answer 3

Hi,

I've also been having the same problem. When editing a list, I'll have to always click on the entries and only be permitted to edit the column settings.

If I ever land on a page with a list and I, as the person who made the website itself, click the column to edit settings or format and etc., I get this error in the console:

**Uncaught (in promise) Error: No ResourceScope available in the current Preact context. Use ResourcesContextProvider to inject a ResourceScope.**This was one of the forums I found that was discussing a similar issue.

Has there been a solution to this?

Answer 4

Thank you for the suggestions, but none work. We've tried switching to SharePoint classic and Teams classic and we still get the same error when trying to open a file from the Teams desktop app.

Answer 5

Dear Alex9522

Good day!

Could you please try to upload the files using Classic SharePoint. (Return to classic SharePoint option at the bottom left corner).

If it still doesn't work, try unchecking "Add a new version to existing files" option on Add a document window.

If you're still experiencing this phenomenon after trying, since you've already found the report in the console, to further help you analyze this phenomenon, I recommend that you contact Microsoft's support staff directly and ask them to assist you in investigating this phenomenon:  Raise a service request in Microsoft 365 admin center

Sincerely,

Tin