there is no coderesources, and info.plist is in the adjacent directory to Plugins (so basically i think it’s looking in the wrong place)
Also, for the files that are present in /Plugins, maybe the reason it’s saying ‘no such file or directory’ is because of the .bundle filename extension?
It’s been less than two business days. I doubt you’ll see any hot patch for something like this. The fact you got any response at all is above average.
Do you have any special characters or space characters in your build path?
Easy enough to test, rename the path to avoid spaces. Yes, it would be a regression on Unity’s part. Software regressions happen. If that’s not the case, we have more data to fix it. If that IS the case, we have more data to fix it AND you are able to continue development before the patch is made.
In the software development world, it is tempting fate to use any special characters or spaces in filenames. There are just WAY too many shell scripts which need very careful handling to deal with paths. It’s always whack-a-mole.
It has been known for some time now!!! It has even been fixed in 2023.x but they didnt even bother backporting it to 2022.2 until i called them out on it !!!
Here is the bug report, its still “under consideration”. Please go an vote for it, nothing much else us poor helpless developers who have invested our lives into unity can do …
Voting on this is pointless, as this bug report is about a specific bug in 2023 (which would only happen for il2cpp universal binary builds with script debugging enabled) - related to code which did not exist in 2022, and with repro steps which don’t reproduce in 2022. It cannot be backported to 2022, and is unrelated to the issue reported here.
