Fix misleading documentation about RoamingSettings persistence through Microsoft Store updates#5671
Fix misleading documentation about RoamingSettings persistence through Microsoft Store updates#5671
Conversation
|
Learn Build status updates of commit b2f36e5:
|
…oft Store updates Co-authored-by: GrantMeStrength <1928855+GrantMeStrength@users.noreply.github.com>
|
Learn Build status updates of commit 46d8c85: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Ipsita - any idea who could confirm this proposed update? Thanks. |
|
this is wrong, localsettings arent persisted either |
…9153112110sync_temp For protected branch, push strategy should use PR and merge to target branch method to work around git push error
|
Closing in favor of PR in the -pr repo. Changes have been applied to the correct file path ( |
The current documentation incorrectly states that "The system also preserves the contents of these data stores when the user installs an update to your app" without clarifying that this doesn't apply to RoamingSettings during Microsoft Store updates.
This issue has been reported by developers who relied on this documentation and discovered their RoamingSettings data was wiped during Store updates, causing data loss for their users.
Changes Made
Updated
/hub/apps/design/app-settings/store-and-retrieve-app-data.md:[!IMPORTANT]warning in the roaming data section explicitly stating that RoamingSettings may not persist through Microsoft Store updatesUpdated
/uwp/get-started/settings-learning-track.md:Impact
These changes provide developers with accurate information about data persistence behavior, preventing potential data loss scenarios. The updates maintain consistency with existing deprecation warnings about roaming being unsupported in Windows 11 while clearly directing developers to use LocalSettings for critical data that must survive app updates.
The documentation now correctly reflects the actual behavior of the Windows app data system during Microsoft Store updates.
Fixes issue where ApplicationData.Current.RoamingSettings does not persist between updates via Microsoft Store.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.