Preview Launch-Based Activation troubleshooting

I am trying to use the preview of event-based activation (https://docs.microsoft.com/en-us/office/dev/add-ins/outlook/autolaunch) but it is proving to be a massively frustrating experience.

I did have it working, I think, at one point using v16.0.14026.20138 of Outlook 365 but I simply cannot get it working again. I have stripped code back to an almost bare minimum to just add a notification message to ensure it's not the code itself, but nothing seems to work. Have tried following the setup instructions and used the yeoman generated solution but that fails too.

The same add-in declares a task pane and that loads absolutely fine. Also, see the event-based activation working absolutely fine in OWA (OnNewMessageCompose).

Expected Behavior

Event-based activation to a) work or b) give an actionable error message

Current Behavior

Two scenarios seem to happen, but I have no idea what triggers one vs the other:

Absolutely nothing happens. No errors
"We're sorry, we couldn't access [add-in name]. Make sure you have a network connection. If the problem continues, please try again later"

The second error seems ideal as it point to soemthing not being right. I cannot find anywhere where this issue would actually be logged though. I tried using the runtime logging, but that is pretty sparse of details, the only thing that seems half-related is:

12/05/2021 16:57:24 Verbose Runtime [Console] [Log] Platform Bundle - Office exists!        
12/05/2021 16:57:24 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions exists!        
12/05/2021 16:57:24 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions.associate exists!      
12/05/2021 16:57:24 Verbose Runtime [Console] [Log] Outlook Batch JS loaded!        
12/05/2021 16:57:24 Verbose Runtime [Console] [Log] Outlook LaunchEvent JS loaded!

I did once see a message related to running the function I had declared, but unfortunately, I do not have that line to hand and cannot reproduce. That appeared to happen whilst I was not looking (i.e. I opened compose window and nothing happened, but when coming back to it later it had run the command)

Steps to Reproduce, or Live Example

I can replicate on multiple machines using our deployed add-in, but would prefer to not share link publically.

Note that this is happening with a hosted add-in, added via. it's manifest URL, and is therefore NOT a localhost problem.

Your Environment

Platform: PC Desktop (multiple versions), Office on the Web
Host: Outlook
Office version number: 16.0.14026.20138
Operation System: Windows 10
Browser: Chrome

Below is our current manifest with text removed and link addresses changed. I can confirm all of those URLs can be loaded.

Anonymised Manifest

- 1.2.0.0 - en-US ReadWriteItem false <Description resid="TaskpaneButton.Tooltip"/> </Supertip> <Icon> <bt:Image size="16" resid="Icon.16x16"/> <bt:Image size="32" resid="Icon.32x32"/> <bt:Image size="80" resid="Icon.80x80"/> </Icon> <Action xsi:type="ShowTaskpane"> <SourceLocation resid="Taskpane.Url"/> </Action> </Control> </Group> </OfficeTab> </ExtensionPoint>  <ExtensionPoint xsi:type="LaunchEvent"> <LaunchEvents> <LaunchEvent Type="OnNewMessageCompose" FunctionName="onMessageComposeHandler"/> <LaunchEvent Type="OnMessageRecipientsChanged" FunctionName="onMessageRecipientsChangedHandler"/> </LaunchEvents>  <SourceLocation resid="WebViewRuntime.Url"/> </ExtensionPoint> </DesktopFormFactor> </Host> </Hosts> <Resources> <bt:Images> <bt:Image id="Icon.16x16" DefaultValue="https://addin-example.com/assets/icon-16.png"/> <bt:Image id="Icon.32x32" DefaultValue="https://addin-example.com/assets/icon-32.png"/> <bt:Image id="Icon.80x80" DefaultValue="https://addin-example.com/assets/icon-80.png"/> </bt:Images> <bt:Urls> <bt:Url id="Taskpane.Url" DefaultValue="https://addin-example.com/taskpane.html"/> <bt:Url id="WebViewRuntime.Url" DefaultValue="https://addin-example.com/commands.html"/>  <bt:Url id="JSRuntime.Url" DefaultValue="https://addin-example.com/commandsdesktop.js"/> </bt:Urls> <bt:ShortStrings> <bt:String id="GroupLabel" DefaultValue="Group Label"/> <bt:String id="TaskpaneButton.Label" DefaultValue="Button Label"/> </bt:ShortStrings> <bt:LongStrings> <bt:String id="TaskpaneButton.Tooltip" DefaultValue="The tooltip"/> </bt:LongStrings> </Resources> </VersionOverrides> </VersionOverrides> </OfficeApp> </details> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Further to above, I'm currently under the impression that this is a javascript syntax / runtime issue. I replaced the file with the absolute bare minimum and changed nothing else and it worked.</p> <p>The Web Add-In Runtime Logging proceeds past "Outlook LaunchEvent JS loaded!" to:</p> <pre><code>13/05/2021 10:32:58 Verbose Runtime [Console] [Log] InvokeMailboxCreateOM was invoked! ... 13/05/2021 10:32:58 Verbose Runtime [Console] [Log] SDX Control is ready! 13/05/2021 10:32:58 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 13/05/2021 10:32:58 Verbose Runtime [Console] [Log] RunLaunchEventHandlerFunctionWithData was invoked with funcName = onMessageComposeHandler 13/05/2021 10:32:58 Verbose Runtime [Console] [Log] Event completed message sent to host! </code></pre> <p>In the case that something is going wrong, whatever that may be, would be great to have some indication in that log file. </p> <p>Still trying to figure out what is going on</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>I've not been able to track down why the issue occurs, but it does seem that if I <code>import {init as initApm} from '@elastic/apm-rum';</code> the resulting code ends up being a problem for M365 Outlook (OWA continues to work).</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>You will not be able to use any imports in the add-in's JS. The JS file has to be one single file and cannot depend on any other files or libraries. A workaround would be to bundle any other files together within the JS file.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc Sorry for the confusion, I <em>do</em> already bundle to a single file using webpack. My comment should have been more explicit.</p> <p>The issue appears to be importing that package ends up creating a bundle that cannot be loaded, in some way, by the desktop JS engine. I cannot narrow it down any more with an error in anyway as I see no error anywhere, just the lack of any further messages in the runtime log</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>The problem here could be that the package you are importing is not compatible with the environment. Are you able to share this package with us if it is public, or is this a private package that you authored?</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc The package is on npm @ <a href="https://www.npmjs.com/package/@elastic/apm-rum">https://www.npmjs.com/package/@elastic/apm-rum</a>. It is <a href="https://www.elastic.co/apm">Elastic APM</a> integration to track performance and errors. </p> <p>It may well be that it makes assumptions about the environment that are not correct (i.e. it expects to be in a full browser environment). If that is the case, then some better error logging is needed from Outlook's side as there would be nothing I can do as it occurs before my code even gets hit</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>We are not familiar with this package. If the package isn't compatible with the environment, our sandbox process will consider the bundle broken. We are investigating how to improve our error logging here for such scenarios. Are you able to achieve your scenario without using this package?</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/ghost"><img src="https://avatars.githubusercontent.com/u/10137?v=4" />ghost</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for <strong>4 days</strong>. It will be closed if no further activity occurs <strong>within 3 days of this comment</strong>. Thank you for your interest in Office Add-ins!</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/ghost"><img src="https://avatars.githubusercontent.com/u/10137?v=4" />ghost</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc We have been able to work around this issue with the APM package, but now development has proceeded I think we are in a similar issue with a different package, or something else entirely.</p> <p>We are now in a position where we have a bundle that will work a few times in a row, but then fail. By failing I mean that nothing happens, and the logs just stop as before. Given the actual JS does not change between retries (because I'm seeing it work and then immediately going back into the New Message dialog to try again) I'm confused.</p> <p>Note that in OWA it works <em>every</em> time.</p> <p>I removed some dependencies, namely i18next and i18next-pseudo and react-i18next and have got to a point of it working again, but not knowing <em>why</em> something is failing is proving very awkward to work with. At any moment a code update can end up in a state that causes problems that appear to be out of our control.</p> <p>The log, with our log lines removed as they are not relevant, is below with the 3 attempts split out:</p> <pre><code>Attempt 1 ========= 18/06/2021 12:08:39 Verbose Runtime [Console] [Log] Platform Bundle - Office exists! 18/06/2021 12:08:39 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions exists! 18/06/2021 12:08:39 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions.associate exists! 18/06/2021 12:08:39 Verbose Runtime [Console] [Log] Outlook Batch JS loaded! 18/06/2021 12:08:39 Verbose Runtime [Console] [Log] Outlook LaunchEvent JS loaded! 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] InvokeMailboxCreateOM was invoked!["{\"hostVersion\":\"16.0.14131.20012\", \"itemType\":4, \"permissionLevel\":3, \"userEmailAddress\":\"th@example.com\", \"userDisplayName\":\"Tom Hanks\", \"userProfileType\":\"office365\", \"userTimeZone\":\"GMT Standard Time\", \"conversationId\":null, \"ewsUrl\":\"https://outlook.office365.com/EWS/Exchange.asmx\", \"restUrl\":\"https://outlook.office.com/api\", \"itemNumber\":6, \"roamingSettings\":\"{}\", \"extensionPointType\":8, \"enableBetaAPIs\":false, \"displayLanguage\":\"en-US\", \"contentLanguage\":\"en-GB\", \"officeVersion\":\"16.0.14131.20012\", \"isFromSharedFolder\":false, \"shouldRunNewCodeForFlags\":1}"] 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] SDX Control is ready! 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] RunLaunchEventHandlerFunctionWithData was invoked with funcName = onMessageComposeHandler 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] Event completed message sent to host! 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] Platform Bundle - Office exists! 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions exists! 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions.associate exists! 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] Outlook Batch JS loaded! 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] Outlook LaunchEvent JS loaded! 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] InvokeMailboxCreateOM was invoked!["{\"hostVersion\":\"16.0.14131.20012\", \"itemType\":4, \"permissionLevel\":3, \"userEmailAddress\":\"th@example.com\", \"userDisplayName\":\"Tom Hanks\", \"userProfileType\":\"office365\", \"userTimeZone\":\"GMT Standard Time\", \"conversationId\":null, \"ewsUrl\":\"https://outlook.office365.com/EWS/Exchange.asmx\", \"restUrl\":\"https://outlook.office.com/api\", \"itemNumber\":9, \"roamingSettings\":\"{}\", \"extensionPointType\":8, \"enableBetaAPIs\":false, \"displayLanguage\":\"en-US\", \"contentLanguage\":\"en-GB\", \"officeVersion\":\"16.0.14131.20012\", \"isFromSharedFolder\":false, \"shouldRunNewCodeForFlags\":1}"] Attempt 2 ========= 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] SDX Control is ready! 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:10:01 Verbose Runtime [Console] [Log] RunLaunchEventHandlerFunctionWithData was invoked with funcName = onMessageComposeHandler 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:40 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] ... 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] MailboxHostExecuteApi invoked! 18/06/2021 12:08:41 Verbose Runtime [Console] [Log] ... 18/06/2021 12:10:02 Verbose Runtime [Console] [Log] Event completed message sent to host! Attempt 3 ========= 18/06/2021 12:10:16 Verbose Runtime [Console] [Log] Platform Bundle - Office exists! 18/06/2021 12:10:16 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions exists! 18/06/2021 12:10:16 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions.associate exists! 18/06/2021 12:10:16 Verbose Runtime [Console] [Log] Outlook Batch JS loaded! 18/06/2021 12:10:16 Verbose Runtime [Console] [Log] Outlook LaunchEvent JS loaded! 18/06/2021 12:10:16 Verbose Runtime [Console] [Log] InvokeMailboxCreateOM was invoked!["{\"hostVersion\":\"16.0.14131.20012\", \"itemType\":4, \"permissionLevel\":3, \"userEmailAddress\":\"th@example.com\", \"userDisplayName\":\"Tom Hanks\", \"userProfileType\":\"office365\", \"userTimeZone\":\"GMT Standard Time\", \"conversationId\":null, \"ewsUrl\":\"https://outlook.office365.com/EWS/Exchange.asmx\", \"restUrl\":\"https://outlook.office.com/api\", \"itemNumber\":12, \"roamingSettings\":\"{}\", \"extensionPointType\":8, \"enableBetaAPIs\":false, \"displayLanguage\":\"en-US\", \"contentLanguage\":\"en-GB\", \"officeVersion\":\"16.0.14131.20012\", \"isFromSharedFolder\":false, \"shouldRunNewCodeForFlags\":1}"] 18/06/2021 12:10:16 Verbose Runtime [Console] [Log] SDX Control is ready! </code></pre> <p>This is using Outlook 365 v2106, Build 14131.20012 on Windows 10. Also seen on Outlook 365 v2105, Build 14026.20308 on Windows 10.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Add-ins in OWA run in a browser. In the native Outlook Desktop client, the add-ins run in a sandboxed environment within a separate process. Are you comfortable sharing your bundle with us so that we can try them in-house to see if we can reproduce this issue? We have never encountered an issue like this.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/ghost"><img src="https://avatars.githubusercontent.com/u/10137?v=4" />ghost</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for <strong>4 days</strong>. It will be closed if no further activity occurs <strong>within 3 days of this comment</strong>. Thank you for your interest in Office Add-ins!</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/ghost"><img src="https://avatars.githubusercontent.com/u/10137?v=4" />ghost</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc we are still experiencing issues here. How can we share more information with you privately?</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>If you can create a private github and give this account access, I can forward it to the product team. </p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc I have added your account to a repro repo at <a href="https://github.com/barclayadam/office-js-launch-repro">https://github.com/barclayadam/office-js-launch-repro</a></p> <p>At the moment it contains just a readme with some details of the issue + access to a VM that has a running Outlook instance pointing at our add-in and associated services that you should be able to replicate the issue with</p> <p>Please let me know what else you would need</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>I tried out the VM and your add-in worked every time I tried it. I tried a total of 10 times. I inspected your bundle which is cached on the VM and I couldn't find anything obvious that was problematic. I must admit that your bundle file was quite large so it is possible I missed something.</p> <p>One thing to know is that we only allow 5 simultaneous instances of your add-in per Outlook session. I don't think that's the issue you are facing right now.</p> <p>I'm in contact with the sandbox team to get instructions on how to get further logging for the sandbox (ULS logs) so that you can share those with us whenever you reproduce this issue.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc thank you for investigating. </p> <p>The almost randomness of the loading issue makes me feel like it's potentially a race condition of sorts, or something similar. There is no pattern that I can discern. I have seen it work 20-30 times before it fails to one once, 10 times can in all likelihood work absolutely fine.</p> <p>The instance limit will not be an issue here.</p> <p>The bundle has a bit of overhead to support Promise (it's polyfilled) and async/await syntax, plus the usual webpack overhead. In terms of the actual code it's pretty simple. I can share if necessary the source if it would help tracking down what is going on here.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>We have continued to investigate this issue and have created a small add-in that shows the issue. The issue is not easy to reproduce and is very non-determinstic, it feels like a race condition.</p> <p>I have updated the readme at <a href="https://github.com/barclayadam/office-js-launch-repro">https://github.com/barclayadam/office-js-launch-repro</a> with details and repros, and included some log files for failures.</p> <p>Would love to progress this as we have customers experiencing issues in production and it appears there is nothing we can do. Happy to get some direct communication going if would help to expedite this issue</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Thank you for the additional information. We are still following up with the sandbox team to get instructions on how to get further logging for the sandbox (ULS logs), as those could be helpful in determining the issue.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Is there any progress on this? Are additional logs going to be available? Sorry to push on this but it affects our production customers and we are at a loss as to what we could possibly do to progress this any further on our side.</p> <p>As a note on loading of add-ins, we have definitely found there are quite some stability issues in Outlook on Windows in general, issues that are different to the above but present in similar ways. Without additional logging though we are, again, unable to make progress or give MS any ideas as to what issues we are hitting</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>To help obtain more logs:</p> <ol> <li> <p>Shutdown Microsoft Outlook.</p> </li> <li> <p>Add the following registry keys:</p> <ul> <li>[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentEcs\Overrides] "of4da4ua5o5tlt1"="true"</li> <li>[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentEcs\Overrides\other] "Microsoft.Office.OEP.SdxSandboxLogTelemetry"="of4da4ua5o5tlt1"</li> </ul> </li> <li> <p>Follow the instructions on this webpage to enable ULS logging: <a href="https://docs.microsoft.com/en-us/office365/troubleshoot/diagnostic-logs/collect-office-diagnostic-logs">https://docs.microsoft.com/en-us/office365/troubleshoot/diagnostic-logs/collect-office-diagnostic-logs</a></p> </li> <li> <p>Reproduce the issue and then exit Outlook.</p> </li> <li> <p>Share the logs with us by adding the log file to your private repo. The location of the log file is specified on the webpage from step 3 above.</p> </li> </ol> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Thank you @exextoc </p> <p>We will be looking at gathering the relevant logs as above this week and sharing them with your as soon as we have them</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>I have uploaded 3 sets of log files to the GitHub repo. Details can be found in the README at <a href="https://github.com/barclayadam/office-js-launch-repro/blob/main/README.md#update-23-09-2021">https://github.com/barclayadam/office-js-launch-repro/blob/main/README.md#update-23-09-2021</a></p> <p>Looking forward to hearing if you can shed any light on what is going on. </p> <p>And once again, would like to extend the invite to have more direct interaction if it would help to solve this issue</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@barclayadam Thank you for sharing the logs.</p> <p>Some of the logs in GitHub appear to be truncated. For instance, the second App<em> file in each directory appears to contain blank lines and the end of the first App</em> file also has blank lines. Do you see the same data on your machine, or is it just a problem with the copy in GitHub?</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc that is indeed like the original files. I noticed a few odd lines in some of the files, but otherwise the files are good. To be sure I have uploaded 3x zip files with the original files, to ensure GitHub rendering / download / upload is not causing more issues</p> <p>I'm sure the blank lines (and basically empty 2nd file) are because Outlook allocates 20mb zeroed files and then writes as much as it has. Leaving empty data at the end of each file, or the complete file in the case it did not write anything to it</p> <p>You can find the 3x zip files at the root of the repo</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc do we know yet if those logs are of any help at all? Quite a lot of information to digest I accept, was hoping there may be something to come from them at all?</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>The sandbox team is looking into the logs to find the root cause of the issue you are observing. PS : Any 404 errors to /.well-known path is ignorable. That is for additional resources in case your add-in supports our Single Sign On APIs. We are actively working on documentation for this.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Thank you for info regarding <code>/.well-known</code>, something like that was my assumption.</p> <p>As a reminder there is a VB script that can be used to automate this failure, where it will also fail in the same way (albeit it takes longer, sometimes much longer, on average), using the sample at <a href="https://github.com/OfficeDev/PnP-OfficeAddins/tree/main/Samples/outlook-set-signature">https://github.com/OfficeDev/PnP-OfficeAddins/tree/main/Samples/outlook-set-signature</a></p> <p>Details are in the linked GitHub repo</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>I tried your VB script. I had to modify it a bit to get it to execute. However, it didn't work as expected because the signature gets inserted after the script has executed. I'm going to try this out again.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>You will find that, depending on what add in you are testing that the signature will get inserted hundreds, maybe thousands of times before it fails (in particular the GitHub hosted PnP sample can take a long time until it fails).</p> <p>It is 100% reproducible eventually, at least on the VMs we have set up, and from customer reports.</p> <p>The idea is the script creates a new email, focuses the body and inserts and X until it can find a signature. Once it finds the signature it will close the window and try again.</p> <p>Also as a reminder, there are two issues I think we are seeing. </p> <p>The "failed to load" message bar appearing. That appears to be an issue with loading the JS/initialising the runtime or similar as the code never executes. This is not hard to reproduce against the MS sample.</p> <p>The other, with calls to the JS API is what I refer to above.</p> <p>If it would be useful to set up any sort of screen share or similar to discuss more as may be difficult to exactly communicate this please let me know</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Let me check if we can setup a meeting to discuss this online.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Thanks for reporting this issue regarding launch based activation. It has been put on our backlog. We unfortunately have no timelines to share at this point.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>So does this mean you can reproduce the issues above? This GH issue became a little muddied with a couple of different issues reported in the end (JS not loading and calls disappearing), can you reproduce both of them?</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 3 years ago</strong> </div> <div class="markdown-body"> <p>Going back to your issue description, there are 2 problems you mentioned.</p> <p>For the second one, we have internal bug tracking it (Office Bug # 5551163). We are actively working on this, however, we have no timelines to share regarding it. This is the bug that results in the error infobar with the message <code>"We're sorry, we couldn't access [add-in name]. Make sure you have a network connection. If the problem continues, please try again later"</code>. The bug here is that our sandbox process experiences crashes for certain users, resulting in a failure to launch the add-in.</p> <p>For the first problem you mentioned, whenever it reproduces, can you check the Windows TaskManager to see if the sandbox process is running? The process name is <code>msoadfsb.exe</code>? We suspect that the crash from the second problem is related to this first problem.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/carlosb1504"><img src="https://avatars.githubusercontent.com/u/47693383?v=4" />carlosb1504</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>We are seeing very similar behaviour with event based activation, we are also using the <code>onMessageCompose</code> event, which has now moved to GA rather than Preview.</p> <p>We see the <code>"We're sorry, we couldn't access [add-in name]. Make sure you have a network connection. If the problem continues, please try again later"</code>. In my testing locally I'm seeing this intermittently using the same js file each time. Similarly to yourself, only in Windows Outlook, works fine in OWA. I believe I've spotted a pattern though, and it's related to the 404 to the /.well-known/ url that was mentioned before. I'm seeing something of a race condition occurring. And it's worth noting that our onMessageCompose method is fairly simple, no SSO API usage etc.</p> <p>My process to reproduce this is to:</p> <ol> <li>clear out the %LOCALAPPDATA%\Microsoft\Office\16.0\Wef\ - this forces Outlook to re-download the onMessageCompose js file.</li> <li>Open a new email, observe in my locally running webserver, 2 requests coming in. One for the /.well-known/ url, and one for the onMessageCompose js file itself.</li> </ol> <p>And the above step is key, the two requests are made in a seemingly random order, which is where the race condition comes in. IF the .well-known request is made first, then I see the problem with the <code>"couldn't access [addin]"</code> message in subsequent new messages. But if the request for the onMessageCompose js file comes in first, then everything seems to work ok for subsequent messages. You need to close the first email which triggered the request for the file in the first place, the second time of asking will reveal whether it's going to work or not.</p> <p>See screenshot below:</p> <p><img src="https://user-images.githubusercontent.com/47693383/143513063-8940f5b9-8c2d-4704-b7d5-668350e6e57f.png" alt="image" /></p> <p>You can see that I've grouped the requests into 4 pairs according to my theory above.</p> <p>pair 1 - call to onMessageCompose.js came first, works OK pair 2 - call to .well-known first, no good pair 3 - no good pair 4 - OK</p> <p>I've tried this quite a few times and the result is pretty consistent. The 404 call does seem to be at fault.</p> <p>I don't recall these .well-known calls being made until recently so I'm assuming this is a new thing.</p> <p>@barclayadam I wonder whether you're able to set up a test similar to the above and see if you get similar results?</p> <p>My next step will be to add the .well-known file to our application in order to satisfy the 404 error and see if this resolves the problem. There are some docs that discuss that here: <a href="https://docs.microsoft.com/en-us/office/dev/add-ins/outlook/use-sso-in-event-based-activation">https://docs.microsoft.com/en-us/office/dev/add-ins/outlook/use-sso-in-event-based-activation</a> although these have only been added in the past few days by the looks of things. I'll feed back with the result of this when I can.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/carlosb1504"><img src="https://avatars.githubusercontent.com/u/47693383?v=4" />carlosb1504</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <blockquote> <p>The sandbox team is looking into the logs to find the root cause of the issue you are observing. PS : Any 404 errors to /.well-known path is ignorable. That is for additional resources in case your add-in supports our Single Sign On APIs. We are actively working on documentation for this.</p> </blockquote> <p>Further to my last comment I can confirm that for us, adding a <code>/.well-known/microsoft-officeaddins-allowed.json</code> file to the server so that a 404 response is avoided, <em>does</em> resolve the problem. See below screenshot:</p> <p><img src="https://user-images.githubusercontent.com/47693383/143594151-59a0f289-38a8-4997-b1cd-093800f5c15a.png" alt="image" /></p> <p>All of the above tries, using the same strategy as in my last post, resulted in a working <code>onMessageCompose</code> file retrieval with the functionality working, and no error message.</p> <p>Further to this, the content of the file does not seem to matter, the same result was observed using both a file containing the add-in's origin domain, as per <a href="https://docs.microsoft.com/en-us/office/dev/add-ins/outlook/use-sso-in-event-based-activation">the docs</a>, and an empty file. It seems as long as the file is present, preventing a 404 response. The outcome is the same. That document also states that we can use a <a href="https://docs.microsoft.com/en-us/office/dev/add-ins/outlook/use-sso-in-event-based-activation#add-a-custom-response-header">custom http response header</a>, but having tested that it does not seem to have any effect at all.</p> <p>@exextoc are you able to advise on this please, what is the status with this functionality and how should we proceed?</p> <p>Also, how can we protect ourselves from these breaking changes? Does the office.js library provide version control via the URL we reference it from so that we can access a reliable copy of it every time, only choosing to get new features when we are ready for them? Having these unpredictable behaviours activated without any warning is not ideal when we have applications in production environments.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>Thank you for the detailed analysis. We are looking into the issue with the additional information.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>We had ignored the .well-known JSON file returning 404 until now. Adding that to return a simple empty file containing <code>{}</code> only does not help to improve our situation.</p> <p>We have got to a point of being able to run our test script to see this working for hundreds of times (typically > 600), but it will still eventually fail in the ways described above.</p> <p>@exextoc we have seen the process <code>msoadfsb.exe</code> crash some times, but could not correlate that process disappearing directly with the failures we are seeing. We saw it crash, but our test was able to continue. I'm not sure if that is helpful, but perhaps point to the <em>when</em> the crash happens in the lifecycle of the add-in being important to final outcome too</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/carlosb1504"><img src="https://avatars.githubusercontent.com/u/47693383?v=4" />carlosb1504</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>How about having the .well-known call return a file with the launch event js URL as per the docs? I'm still seeing this issue and can reliably reproduce fixing it by serving this file. It's important to clear that 'Wef' folder on the machine with Outlook closed to force Outlook to re-attempt to retrieve your js files, as it's doing some internal caching which can mask the problem</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>@carlosb1504, thanks for your input here.</p> <p>@barclayadam when msoadfsb.exe crashes, can you check the Windows Event Viewer for crash reports to confirm this?</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc We have a number of customers in production that, for a handful of users, see a crash of the <code>msoadfsb</code> executable every time they create a new message, with the result being no event-based activation and "We're sorry, we couldn't access [add-in name]. Make sure you have a network connection. If the problem continues, please try again later" message bar is shown.</p> <p>The add-in works fine for many other users in the same tenant, and in OWA, but causes the crash consistently for at least one user on multiple machines.</p> <p>I have added to the private repo some additional details and logs. Update in README at <a href="https://github.com/barclayadam/office-js-launch-repro/blob/main/README.md#update-05-01-2022---instant-crash">https://github.com/barclayadam/office-js-launch-repro/blob/main/README.md#update-05-01-2022---instant-crash</a></p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc As above we continue to have numerous customers that experience the issue of the add-in not loading. Typically we are seeing just one, or perhaps two users that have the issue out of the whole M365 tenant. We have:</p> <ul> <li>Upgraded some user's Outlook and the problem has gone away</li> <li>Upgraded some user's Outlook and the problem has <strong>not</strong> gone away</li> <li><strong>Not</strong> seen the <code>msoadfsb.exe</code> process crash in most of these instances. The error, once it has manifested itself will be shown on subsequent message compose attempts <em>immediately</em></li> <li>Removed the add-in from admin deployment and installed manually, the problem has <strong>not</strong> been fixed</li> <li>Seen users where the same problem exists for them on multiple machines</li> <li>Seen users where the same problem does <strong>not</strong> exist on different machines</li> <li>On a development machine we have killed Edge and seen the problem go away for a period of time</li> </ul> <p>We are running out of steam on what to try with our customers as there is <strong>zero</strong> information given about what the problem could be. We know the JS is being loaded on Outlook launch as we can watch the network traffic. And we know it's not running any of our code as there is nothing in the runtime logs. </p> <p>We really need assistance directly from somebody in the team to help to diagnose this issue and why it happens to only a small handful of our customers</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/exextoc"><img src="https://avatars.githubusercontent.com/u/28549921?v=4" />exextoc</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>@barclayadam thanks for the update. We have addressed some bugs in msoadfsb.exe that could be the reason why the issue is fixed for some users. And for the .well-known issue, please don't use an empty file. Having the file will help users on older builds that have the bug that is addressed by adding this file. I have alerted the sandbox team to look into the crash in msoadfsb.exe. Thanks for adding more information regarding this to the private repo. Since you have multiple users having multiple different problems, it is likely that these users have different buckets of issues. Drop your contact information in the private repository and I will contact you via email so that we can setup further communication and then circle back to this thread with our findings.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc I have updated the readme with my email address, I look forward to hearing from you.</p> <p>We do not return an empty .well-known file in production, I was only testing with different variants before. </p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/barclayadam"><img src="https://avatars.githubusercontent.com/u/973909?v=4" />barclayadam</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>@exextoc we are continuing to experience new users hitting this issue, and it is becoming pressing now with many customers having a handful of users with errors. We have one customer that, from around 400 users has 5 that do not work. </p> <p>They have updated their Outlook (we are not yet sure what release channel they are on, but we do have customers on the current channel with the same behaviour) and nothing changes.</p> <p>This is becoming more of a problem every day and we would love to get this sorted. It is becoming business-critical</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/JuaneloJuanelo"><img src="https://avatars.githubusercontent.com/u/8866386?v=4" />JuaneloJuanelo</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>FYI to all our community we are following up directly with @barclayadam and his team. Turns out its been tough for our engineering team to repro this issue, however we have a customer who has shared an environment and we are investigating. thanks for the patience. </p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/jbrookins13"><img src="https://avatars.githubusercontent.com/u/1474509?v=4" />jbrookins13</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>@JuaneloJuanelo Any update on this? Working on a critical Outlook add-in, and I'm getting the "We're sorry, we couldn't access [add-in name]. Make sure you have a network connection. If the problem continues, please try again later" once I added <code>LaunchEvents</code> to the manifest. Works as expected in web Outlook client.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/ElizabethSamuel-MSFT"><img src="https://avatars.githubusercontent.com/u/28541963?v=4" />ElizabethSamuel-MSFT</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>@jbrookins13 Can you create a new issue with details about your own scenario, configuration, etc.?</p> <p>Thanks.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/JuaneloJuanelo"><img src="https://avatars.githubusercontent.com/u/8866386?v=4" />JuaneloJuanelo</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>Hello, I want to provide an update for this issue. Thanks to a close collaboration with a few of you (@barclayadam team specifically) we were able to find the root cause issue [BTW although is affecting a small % of users of this feature, the behavior is unacceptable]. The good news is that the issue is fixed! We are working to roll it out to production, and it will make it into the next "Patch Tuesday" event which happens on May 10th. We will back port this fix to the previous semiannual channel as well. </p> <p>If your development is blocked or some of your customers trying your add-in are failing because of this, please email me at <a href="mailto:juanbl@microsoft.com">juanbl@microsoft.com</a> to work on a potential workaround.</p> </div> </div> <div class="page-bar-simple"> <a href="/OfficeDev/office-js/1861?page=2" class="next">Next</a> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>

OfficeDev / office-js