StefanoAnzolut
commented
1 month ago As mentioned by Patrick Rodgers, in the community post above a fix is now rolling out. So I'll close this issue. Thanks.
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.
As the filehandler is related to OneDrive development. This issue should also be raised directly here. First appeared and reported this month by the user Alex9522 in the Microsoft community forum. https://answers.microsoft.com/en-us/msoffice/forum/all/cannot-initialize-addon-without-a-resourcescope/f8fce3e3-1d42-43b1-92b1-578b2d876309
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.
Category
Expected or Desired Behavior
In a different tenant, opening the files from Teams still works. 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.jsThe older file doesn't throw that error.Observed Behavior
In Chrome DevTools we can see that error "Cannot initialize Addon without a ResourceScope" in the Console, originating from
spofilehandlerproxy.js. The page remains blank. 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.jsIt is only thrown with this new version.Steps to Reproduce
Open a file from Teams in a SharePoint file handler app.