We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Related to 21474
Standard backup file changes the profile settings to custom ones, which leads to a failure in the selection of Units & Formats categories
Delete all data - simulate the first startup with default profiles (restoring the default settings does not help)
After export (importing) the osf file, the default settings are replaced with custom ones (although no replacement has been made)
What makes it impossible to change data in Units & Formats categories
When exporting (importing) data, the data retains its standard form and cannot be changed
WARNING Crash-Logs MAY contain information you deem sensitive. Review this CAREFULLY before posting your issue!
OsmAnd Version: OsmAnd~ 5.0.0#3834m, Released: 2024-11-28 Android/iOS version: Android 14 Device model: Crash-Logs: ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
Related to 21474
Standard backup file changes the profile settings to custom ones, which leads to a failure in the selection of Units & Formats categories
Steps to reproduce
Delete all data - simulate the first startup with default profiles (restoring the default settings does not help)
Actual result
After export (importing) the osf file, the default settings are replaced with custom ones (although no replacement has been made)
What makes it impossible to change data in Units & Formats categories
Expected result
When exporting (importing) data, the data retains its standard form and cannot be changed
Your Environment (required)
WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!
The text was updated successfully, but these errors were encountered: