Allure 3 Fails to Open With Azure Allure Report v2.1.4

[krypton1981]

I am on v2.1.4 of the Allure Report extension in ADO. When I try to click on the tab to load Allure3 report I am given this screen:

Pinning to version 2.36.0 while using PublishAllureReport@2 allows the report to load without error.

[keegan-conlee-IM]

I'm having the same issue. However, pinning the report version to v2 isn't feasible for me, as I need some features that only exist in allure v3 (such as displaying playwright traces). The generate allure report task doesn't log any errors. I also see that both the allure.report.info and allure.report.summary requests in the network tab return {"count":0,"value":[]}.

Also, when I go into the ADO agent's work directory, I do find an index.html generated, but when I open it, it looks like this:

[keegan-conlee-IM]

It looks like the task is using allure version 3.0.1. Specifying allureVersion in the pipeline YAML did nothing except make the extension try to download a version of allure 3 from the allure2 repository, however running npm update in the plugin's directory in C:\agent\_work\_tasks did successfully update allure to version 3.3.1. It didn't change either of the above issues though.

[dataport-david]

I found the Error in the index.js in the 2.1.4 folder of the allure task C:\agent_work_tasks on the agent.
Line 203 and 236 return empty on windows clients.
summaryFiles = await fg([path.join(tempReportDir, "**", "summary.json")], { onlyFiles: true, });
The "**" doesn't work for windows and the function returns empty for summaryFiles.
Because of this the for loop after gets skipped and there is no upload of files for Allure 3 on windows clients. That's also why there is no error message.

I manually edited the index.js on all my agents and now it works except for the bug in singleFile reports that keegan mentioned. That should be fixed when the included files of Allure 3 in the plugin get updated from v3.0.1 to v3.4.0.