Closed chucklay closed 7 months ago
@jeremy-msft can you provide insight about the change from IE to Edge as the default browser for shared runtime? @lumine2008 can you provide further assistance on reverting to individual run times? @chucklay is the browser issue why you want to revert to the individual run times? Or is there another issue blocking you from using the shared runtime?
@KelBowen Yes, we've found that debugging in edge-based web views is a much smoother experience. Plus, one of the things our add-in does is pull data from our database and stick it in spreadsheets. Some of these tables are pretty large, so when we send out a request to pull the data, the response ends up being pretty hefty. On modern browsers this isn't an issue as we're able to stream the responses and manage them in reasonably-sized chunks. However, there's no way to do this in IE, so it ends up trying to load the whole response at once, which is more than it can handle.
The add-in still works in IE11, with the caveat that Edge or another modern browser might be required if someone wants to load a large table, which is a compromise we're more than willing to accept, since none of our clients use IE11 (and being totally honest, if it were an option we would drop support for IE11 completely - ensuring compatibility has been way more trouble than it's worth)
One thing I've noticed just now: the add-in sometimes loads with the error message after ~a minute, but sometimes the loading screen just hangs indefinitely. When it hangs indefinitely, the "We're starting the add-ins runtime, please wait a moment..." message is also stuck on the bottom of the screen.
I've also noticed (and this is essentially speculation at this point) some behavior that almost seems like it's trying to open the add-in twice. Clicking the taskpane toggle again after waiting for my add-in to load (with the error message) it opens a second taskpane tab instead of hiding the existing taskpane. In addition, another dev who tried to load my changes had the "Using multiple taskpanes?" notice pop up. I'd suspect some kind of circular reference but I don't see anything in the logs or my code that would suggest that.
Hi @chucklay, Re: Edge support for shared runtime, please see @smaremanda's comment here about timelines. This should be rolling out soon.
@jeremy-msft Fantastic! Thanks!
I still really need some help getting my add-in to load. I've rolled back to a version that I know works (using a shared runtime), but I'm still getting a blank taskpane (now without a loading spinner). OfficeAddins.log.txt still doesn't provide any useful information, and again, this is only happening on desktop. It loads perfectly fine in every browser I try.
It seems like debugging/logging the add-in as it actually loads could use some major improvement. I feel like every time I modify my manifest in any way, there's a 50% chance I'm going to have to spend the rest of the day (or week in this case) feeling around in the dark trying to fix a problem I get no feedback on.
I don't want to open a new issue on it but shared runtime absolutely not working with webview2 on the latest excel build (even with the latest beta 13707.200008)
System: Windos10 Webview: webview2 Env. : sharedruntime addin : excel symptom: taskpane not loading (https://github.com/MicrosoftEdge/WebView2Feedback/issues/820#issuecomment-760580110) same manifest.xml works well on office web,
Including @smaremanda for the reported WebView2 issue.
@smaremanda, can you help take a look at this issue?
@jeremy-msft Any update on this? Please reassign if you're not the right person for this.
Thanks.
This is a weird one. I'm attempting to switch my Excel add-in back to individual runtimes instead of a shared runtime. (on a related note - is there any timeframe on when we can expect add-ins that use shared runtimes to use edge-based web views instead of IE-based?) I have everything working on excel on the web, but when I try to open the taskpane on desktop Excel, it sticks for about a minute on the loading spinner, then eventually shows the "Add-in error: This add-in could not be started" banner, but as soon as that banner pops up, my add-in loads:
It seems to run fine once it loads, and I don't see any errors or problems in the browser console or any logs that I can find, so I have no idea where the issue is.
Expected Behavior
My add-in should load without displaying an error message.
Current Behavior
My add-in eventually loads, but displays an error message in the proccess
Steps to Reproduce, or Live Example
I assume the issue is probably related to my manifest, so this is what it looks like:
npm run validate
claims that my IconUrl and HighResolutionIconUrl are unreachable, even though they are. I'll post the full output in the logs sectionContext
This is preventing me from switching back to individual runtimes.
Your Environment
Useful logs
OfficeAddins.log.txt:
Interesting to note that I don't have a Runtimes section anymore, so I'm not sure why that's showing up. The only other add-in I have installed is ScriptLab.