-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failure updating macOS client from 3.12.7 -> 3.12.8 #743
Comments
@gorgatron1 Are you running the App or the legacy macOS installation (command line)? |
Here is where it fails to create it but no indication what the error was:
The path in the second line is curious -- that leading |
I guess I am probably running the legacy install -- it has been upgrading itself all along and has been in the directory where it always was. |
Understood. This is likely a bug, however would you be interested in running the App? I can see the legacy installer being deprecated. Now that we have a working app IMO we should continue spending our efforts there. |
Sure, I can switch to it. The legacy installer is actually easier for me, but I know it isn't for everyone. |
It is easier? What makes it easier? We might want to continue support if there is value in the command line over the App. |
Well, I am a developer so running things from the command line (Terminal) is super easy. I like the fact that it can update itself and I don't need to manually download dmgs and mess with the quarantine:
but most Mac users probably aren't using the command line so this isn't as convenient for them. |
Don't keep it around just for me! |
Oh and maybe the .app will update itself -- that would explain downloading the .jar to that Application Support directory |
The App should update itself. |
There was a bug in 3.12.7 that prevented the app from updating itself. Please install 3.12.8 manually. Going forward it will update itself (unless we missed something). Edit to add: Hopefully, the quarantine is just a one-time thing at the initial download/install. Once it is installed and updating itself correctly you shouldn't have to do that. |
@gorgatron1 Can you confirm this is now working as expected? |
Describe the bug
failure updating macOS client from 3.12.7 -> 3.12.8
To Reproduce
Here are the logs from the client (where I think the failure happens -- the server seems to be updated):
I am not sure why it is referring to
/Users/dkoski/Library/Application Support/VPin-Studio/
-- the client is installed in/Users/dkoski/pinball/VPin-Studio-Client-macosx_aarch64
but maybe the plan is to move it there?Anyway, here is the contents of the directory -- no
update-client.sh
:The text was updated successfully, but these errors were encountered: