[BUG] removing legacyFiles is not working if legacyFolders is not specified #299
Assignees
Labels
bug
Something isn't working
Comments
|
I confirmed this issue still exists in 2.1.2 |
|
Thanks! This should be fixed in the next release. |
|
I confirmed this still is a issue in VCC 2.2.2.... |
|
Thank you for your response, much appreciated.
…On Wed, Dec 13, 2023, 8:44 PM anatawa12 ***@***.***> wrote:
I confirmed this still is a issue in VCC 2.2.2....
—
Reply to this email directly, view it on GitHub
<#299 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFUEYHZMFTVLQX5QLDVVULYJJ7ZBAVCNFSM6AAAAAAYJIGHVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVGEZDANRQGU>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
|
bump. this is still a issue in VCC 2.2.5. |
|
This should be addressed in the 2.3.0 open beta: https://github.com/vrchat-community/creator-companion/releases/tag/2.3.0 |
|
This has been released to live with version 2.3.0: https://vrcpm.vrchat.cloud/vcc/Builds/2.3.0/VRChat_CreatorCompanion_Setup_2.3.0.exe |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
removing legacyFiles is not working if legacyFolders is not specified
To Reproduce
Legacy File with NameorLegacy File With PathExpected behavior
Assets/legacyFileWithName.txtorAssets/legacyFileWithPath.txtshould be removedScreenshots
No response
Related Product
VCC (VRChat Creator Companion)
Product Version
2.1.1
OS
Windows 11
Additional context
There are no logs like
Looking for Legacy Packages to Upgrade by Scanning Folders within <package>when we're installingLegacy File with NameorLegacy File With PathIf we added legacyFolders attribute,
Looking for Legacy Packages to Upgrade by Scanning Folders within <package>is shown but because of #281, no files are removed. (you can test withlegacyFiles with Name with legacyFolderspackage from same repository)The text was updated successfully, but these errors were encountered: