mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-27 08:45:50 +03:00
[GH-ISSUE #1003] [Bug]: PlayCover is immune to settings set in GUI or editing plist file #517
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#517
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mavethee on GitHub (Jun 17, 2023).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1003
Describe the bug
Trying to change settings of any app, back-frames all my changes, that's known issue so I re-open settings to make sure certain settings were set, trying launch the game will keep previous settings (e.g when reset to the default and want to change aspect ratio to 16:10 again).
Steps to reproduce
Use PlayCover 3.0 beta1 on macOS 14 Sonoma Beta 1 (23A5257q)
Preferably reset app settings to default, try switching back to 16:10 again or high res.
Expected behaviour
Applied settings working correctly.
Crash log
No response
What version of PlayCover are you using?
Nightly/beta
What version of macOS are you using?
macOS beta (please state the specific version)
Issue Language
@MEMORIEmusic commented on GitHub (Jun 17, 2023):
This is (most probably) a macOS Sonoma issue. It doesn’t occur on Ventura and below.
@mavethee commented on GitHub (Jun 17, 2023):
Well that's I've mentioned in issue description I assume, question is if it's an issue more like for Sonoma stable release to check out on or can be looked on at current state.
@mavethee commented on GitHub (Jul 17, 2023):
Any ideas on potential fix or we will have to wait for official release?
@TheMoonThatRises commented on GitHub (Sep 2, 2023):
Fixed in later Sonoma beta.