Closed waya0125 closed 8 months ago
I believe 916d5a65 should fix the issue, but I don't have apple silicon mac. Would you try this artifact of the workflow job?: https://github.com/kurotu/tiny_vcc/actions/runs/6439011224
Got it. I'll check it.
Sorry, but I don't know how to initialize the application settings in a Mac environment. Once Install is done, I need to blow up the settings, but it seems that just erasing the package is not enough. Do you know anything about this?
Sorry for inconvenience, you need to remove existing Unity Editor and reset VCC settings.
/Applications/Unity/Hub/Editor/2019.4.31f1
~/.local/share/VRChatCreatorCompanion/settings.json
/// Clear pathToUnityExe and unityEditors values. Keep other parameters as is.
{
"pathToUnityExe": "",
"unityEditors": []
}
Please let me know if it seems hard to test. I'll release the bugfix as is.
It's probably not working correctly. It's stopped in the same place as last time.
Sorry again, I forgot to let you know. Please make sure you are using Unity Hub 3.5.1 or later.
I using Unity Hub 3.5.2
Thank you for kind feedback. I'll investigate more.
Thanks you.
When I looked it up, I was glaring that this might be the cause because there is a warning message at the beginning that occurs when updating to macOS Sonoma.
I made a new artifact: https://github.com/kurotu/tiny_vcc/suites/17068682673/artifacts/974918616 The problem was architecture detection in tiny vcc's code.
"Secure coding" sentence seems just a warning for Unity Hub on Sonoma. I think it's not related to this issue.
Ok. I'll check it out now. Sorry for the irrelevant remarks.
OK, working.
Ahhhh, I was able to install it, but I can't recognize the installed file and it will be an error judgment.
Unity Hub CLI's output is different on Apple Silicon, so version detection failed. Sorry to bother you again, I made a new artifact to fix: https://github.com/kurotu/tiny_vcc/suites/17112075644/artifacts/977497951
I believe this is the last one because Unity Hub part is all done.
I can now get information from Unity Hub correctly, but it can be written even if it is not Unity 2019.4.31f1, is it okay?
Thank you for testing. At least now we can get unity installed, so I can inspect further behavior on my Mac. Would you execute Unity Hub in terminal? I'll check it with #4.
/Applications/Unity\ Hub.app/Contents/MacOS/Unity\ Hub -- --headless editors --installed
I was late in confirming. My apologies. I'll try to run it right after this.
Unity that comes at the top is automatically assigned, so if 2019 is not included, the installation should be executed, but it is no longer executed.
I added version check for the issue above. But it originally relies on vpm check unity
, so the issue may happen. In such case, please manually install appropriate unity.
When I specified it by hand, it started to work. I'm sorry to trouble you for a long time.
v0.6.0 should fix the issue. Thank you for kind cooperation.
Describe the bug Install is not running properly
To Reproduce Press the install button, that's all.
Expected behavior Probably, but the type of CPU is being asked at the time of installation, so I think it would be good to solve it.
Screenshots It is japanese text. I'm so sorry.
Desktop (please complete the following information):