Cider Experimental ARM build crashes on launch

[Mistashio]

Preflight Checklist

• [x] I agree to follow the Code of Conduct that this project adheres to.
• [x] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• [x] I have confirmed that no support FAQ resolves my issue.
• [x] I have checked that the correct behavior occurs on Apple Music Web (if applicable).
• [x] I have verified that my issue is with a supported version and that it is with the desktop app (Support for other areas can be found in our Discord / on the appropriate repo).

How did you download Cider?

Taproom

App Information

Build ID (from Taproom): 69e97d06407434d2d44adc0785610b54-132

Operating System

Windows

OS Version

Windows 11 (ARM)

How would you describe your issue?

Frontend

Commit Hash

i dont know how to find this and the app won't open

Describe the Bug

When opening Cider, it shows the loading window for a moment, it pauses, then closes, the Cider Node Runtime is left running in the background as well and has to be manually closed.

Expected behavior: Cider opens and shows the first-launch setup

Steps to Reproduce

1. Download and install the arm64 experimental build of Cider on an ARM PC
2. Launch Cider

Anything else?

I am using a Surface Pro 11 w/ the Snapdragon X Elite processor, the normal x64 cider works ok, albeit slowly so I wanted to try the ARM build even if it was experimental

[cider-collective[bot]]

Hello @Mistashio 👋

We really appreciate you taking the time to report this issue! Please double-check your report to ensure your description is clear and concise—this will help us assist you as quickly as possible.

We kindly ask for your patience, and we'll get back to you as soon as we can.

In the meantime, feel free to check out our FAQs, which may have the answer to your question.

Thanks again, and we hope you enjoy the app! 😃

[cider-collective[bot]]

Hello again!

We've noticed that you haven't replied in a while. Unfortunately, our team isn't always able to address issues as quickly as we'd like. To help us assist you more efficiently, please provide the following information:

1. Ensure your client is as up-to-date as possible. You can do this by using the experimental release on Taproom (if available) and the PTB release through the in-app updater.
2. Let us know if the issue is still present. If it is, please provide the version you're using and mention any changes you've noticed since reporting the issue.

This information will help us identify whether the issue has already been resolved.

Please try to update us within the next 20 days; otherwise, we will close this issue.

Thanks for your help! :smiley:

[Mistashio]

1. I installed the ARM version again through taproom, same version was available
2. Yes the issue is present and exactly the same, nothing changed

[cider-collective[bot]]

Hello again!

We've noticed that you haven't replied in a while. Unfortunately, our team isn't always able to address issues as quickly as we'd like. To help us assist you more efficiently, please provide the following information:

1. Ensure your client is as up-to-date as possible. You can do this by using the experimental release on Taproom (if available) and the PTB release through the in-app updater.
2. Let us know if the issue is still present. If it is, please provide the version you're using and mention any changes you've noticed since reporting the issue.

This information will help us identify whether the issue has already been resolved.

Please try to update us within the next 20 days; otherwise, we will close this issue.

Thanks for your help! :smiley:

[cider-collective[bot]]

Hello!

We have closed this issue due to inactivity. If you are still experiencing this bug in a supported version, please open a new issue with the necessary information.

Thank you for your understanding! 👋