App with every start reset position and size

[MrCrowCZ]

Preflight Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• I have checked that the correct behavior occurs on Apple Music Web (if applicable).
• 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).

Download Source

Microsoft Store

Operating System

Windows 11

Commit Hash

766652aa4212508de014b6233c338b6e9b41ff37

Connect Instance ID

No response

Build Timestamp

No response

Describe the Bug

If not a bug, then it's suggestion to change that.

Everytime when I open the cider app it always open at the same place on the same screen. Since I have (and probably more people) more than 1 screen would be great if the app remember last position and size.

Even the fancyzones from powertoys cannot "override" the position

Steps to Reproduce

Open the app. Move it to different screen. Close the app. Open the app again. Voila.

Anything else?

No response

[github-actions]

Hello @MrCrowCZ 👋

We really appreciate you taking the time to report this issue, please double check your issue to make sure you are clear and concise in your description. This will help us to help you as quickly as possible.

We'd like to ask you be patient and we will get back to you as soon as we can.

In the meantime, take a look at our FAQs which may answer your question.

Thanks again and we hope you enjoy the app! 😃

[TheFirstComix]

this is true facts it always happens to me too

[github-actions]

This issue is stale. If this issue is still occurring and you are on a supported version, please leave any comment (e.g. "bump") within the next 7 days and the issue will remain open. If you have any additional information that may help us resolve your issue, please include it with your comment.

[github-actions]

This issue has been closed due to inactivity. If you find this bug to still be occurring in a supported version, please open a new issue with the necessary information.