-
Notifications
You must be signed in to change notification settings - Fork 223
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
Support Squirrel flag JSON output for SUFeedURL - Sparkle #1304
Comments
Hi @rishimodha, Thanks for bringing up this issue to our notice. Now, we have added the support of Squirrel JSON format.
Please let us know your experience on this and get back to us if you have any other concerns/requirements. |
@Ajaykn21 thanks for adding this. If possible, can you add handling to redirect the HockeyApp URL that contains the squirrel tag to the corresponding AppCenter URL with the squirrel tag? |
Yeah @rishimodha, we are working on this already and will update over here once it is ready. |
@Ajaykn21 - Any update on this? |
@rishimodha , we are flooded with other priority requests. We have started working on this and will update you once done. |
@rishimodha, we have released this to Production. Example: Although, it is recommended to update your apps SUFeedUrl to AppCenter Sparkle feed url. |
@Ajaykn21 Yes, this working great. Thank you! |
@rishimodha can we close this issue, as this is already fixed ? |
Describe the solution you'd like
Support the Squirrel flag for the Sparkle update feed. This was supported on HockeyApp and it is required for Electron AutoUpdater, which does not support XML output and requires JSON. See example: https://rink.hockeyapp.net/api/2/apps/bc02347d258a40e2af46cc8de3566bab.json?squirrel=true
Describe alternatives you've considered
It won't be possible for us to complete the transition to AppCenter from HockeyApp until support for Squirrel JSON format is added. Please do not force a transition before this is supported as it will cut off our customer's ability to update their apps.
The text was updated successfully, but these errors were encountered: