Closed wh1t3cAt1k closed 1 week ago
Thank you for letting us know about this issue. We will take a look shortly. Thanks.
Note that there are two reference IDs in webextension1.xml
inside the file structure. They differ only by case and by store value.
Does anything here looks unexpected and suspicious? I can guarantee that this file has not been manually tampered with but it was opened on both Excel Online and Excel for Mac.
Also, this file works just fine on Excel for Mac so it is an Excel Online-specific issue.
Once I manually convert the reference ID to uppercase (I suspect I didn't even have to remove the alternate references):
The file opens without any problems.
Guys, this seems like an easy fix to handle on the Excel's side? You could either
.toUpper()
on any reference ID encountered when processing web extension references?I think that manually fixing the files is not a good option here and I'd rather have an in-product fix.
In conclusion, I think this is the same as #3993, just a new instance of the same issue... Maybe a fix could be expedited?
Duplicate of #3993
Summary
Upon opening of the following file,
await Office.addin.setStartupBehavior(Office.StartupBehavior.load);
or anyExcel.run(...)
calls hang indefinitely during our add-in's start-up sequence so it cannot initialise.Sage Intacct Demo GM Fixed.xlsx
Session ID: 035bc6eb-68f2-2001-b9d2-b2f9d9092f3a
There are no suspicious errors in the console so it's impossible to understand what went wrong.
The issue replicates only on a subset of files, so it might be because of an internal metadata issue.
UPD: this is confirmed, see below
Your Environment
Expected behavior
The file to open and the add-in to start without any problems.
Current behavior
The add-in cannot interact with the Excel API because it simply hangs.
Steps to reproduce
Velixo internal tracking item