Skip to content
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

Automatic Update issue #53

Open
c-o-m-m-a-n-d-e-r opened this issue Oct 2, 2016 · 14 comments
Open

Automatic Update issue #53

c-o-m-m-a-n-d-e-r opened this issue Oct 2, 2016 · 14 comments
Labels

Comments

@c-o-m-m-a-n-d-e-r
Copy link
Collaborator

Hey,
i recently create Version 2.5 with Fix for the Dock Badge and Swift 3 changes.
I also tried updating via auto update (make the changes) but extracting failed...

Whats going wrong?

@VagishVela
Copy link
Owner

@c-o-m-m-a-n-d-e-r Not sure if it has to be created by the same user? Might be some mismatch between the Neo11 package and yours?

@c-o-m-m-a-n-d-e-r
Copy link
Collaborator Author

c-o-m-m-a-n-d-e-r commented Oct 4, 2016

don't think so, its just the github release function with sparkle updater...
this is only points to the release url ...download works but extracting fails ...

Will try again with a beta relase soon (i have working my version now, you can download direct via Release Page)

Ok i found an info for that, seems to be the code sign in deed ... mhhhh

@c-o-m-m-a-n-d-e-r
Copy link
Collaborator Author

Solved Problem by creating own DSA Signature...
I made subrelease 2.5.1 ... could you please check (just restart ChitChat)

@maciboy
Copy link

maciboy commented Oct 4, 2016

Extraction of 2.5.1 with automatic update failed for me (several tries)

@c-o-m-m-a-n-d-e-r
Copy link
Collaborator Author

okay, sounds bad ... could you please try with V2.5 and then update via auto update to 2.5.1?

https://github.com/Neo11/ChitChat/releases/download/2.5/ChitChat.zip

V2.5 is first build of me ... but it seem SU checks the Creator too ...

@maciboy
Copy link

maciboy commented Oct 4, 2016

That worked :)

@c-o-m-m-a-n-d-e-r
Copy link
Collaborator Author

@Neo11 : Autoupdate only works with one Dev Account. If we change it to my you have to deliver one update with my DSA Public Key.
Do you want to make Release in Future? Or should we change to me? your decission ...

In Fact :
Everyone can manual update to 2.5 (or 2.5.1) and is ready for further release of my account... we should talk about a plan for this :)

@Neo11
Copy link
Collaborator

Neo11 commented Oct 9, 2016

Think I should build the releases. This way there will be less confusion.
I uploaded a 2.5.2 Version, maybe we should use this soon in the update file with a little notice about the different signing keys in 2.5?

@VagishVela
Copy link
Owner

@Neo11 Some things were merged in recently, can you create a new build?

@Neo11
Copy link
Collaborator

Neo11 commented Jan 24, 2017

I have no Xcode anymore, so someone other must build.

@VagishVela
Copy link
Owner

@Neo11 Did you want me to take over the repo as well? I can keep it up to date.

@Neo11
Copy link
Collaborator

Neo11 commented Jan 24, 2017

I think this would be good.

@VagishVela
Copy link
Owner

@Neo11 Feel free to transfer ownership to me.

@VagishVela
Copy link
Owner

@Neo11 I'll get it updated and hopefully also setup an auto deploy so we can automate some of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants