Error when reading or writting files in rmarkdown

[Pierre9344]

Hello,

I get the following error when I try to write a file from a rmarkdown document (I use the quarto package to render my document).

ARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.poi.util.SAXHelper (file:/C:/Users/PierreS/AppData/Local/R/win-library/4.2/xlsxjars/java/poi-ooxml-3.10.1-20140818.jar) to method com.sun.org.apache.xerces.internal.util.SecurityManager.setEntityExpansionLimit(int)
WARNING: Please consider reporting this to the maintainers of org.apache.poi.util.SAXHelper
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Quitting from lines 4981-4984 (4_longmixr_v2.qmd)
Error in .jcall(wb, "Lorg/apache/poi/ss/usermodel/Sheet;", "createSheet", :
java.lang.IllegalArgumentException: The workbook already contains a sheet of this name
Calls: .main ... eval -> write.xlsx -> createSheet -> .jcall -> .jcheck

I have a similar warning when I try to read the documents.

Any idea of how I can resolve it?

I thank you in advance.

[Pierre9344]

Sorry for the double post, the error I have here provoqued a bug because there was another sheet with the same name already. This is what produced the error that stopped the rendering of my document.
Generally, I only have the next warning when I use read.xlsx:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.poi.util.SAXHelper (file:/C:/Users/PierreS/AppData/Local/R/win-library/4.2/xlsxjars/java/poi-ooxml-3.10.1-20140818.jar) to method com.sun.org.apache.xerces.internal.util.SecurityManager.setEntityExpansionLimit(int)
WARNING: Please consider reporting this to the maintainers of org.apache.poi.util.SAXHelper
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

[colearendt]

Interesting! This seems like it may be an issue with the older Java library. Would you mind giving the newer branch a shot to see if it fixes?

Directions here: #142 (comment)