Skip to content
New issue

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

Cloud sync between two freshly installed apps on iPadOS and iOS produces sync errors / warnings #3936

Closed
maxmeyer opened this issue Aug 16, 2024 · 8 comments
Labels
Milestone

Comments

@maxmeyer
Copy link

maxmeyer commented Aug 16, 2024

Issue

I"m not able to get a clean sync between an iPad and an iOS device using the OsmAnd Cloud sync after a cleared cloud and removed/reinstalled apps on both devices:

Steps to reproduce

  1. Setup of Cloud + Abo
  2. First sync between devices
  3. Sync conflicts occurred after a crash of OsmAnd on the iPad while syncing maps
  4. Cleared cloud using the iOS App
  5. Remove apps from iOS and iPad
  6. Setup apps again with no locally installed maps
  7. Start sync on first device - wait till the sync is finished successfully (green arrow)
  8. Start sync on second device
  9. Sync conflicts occure on second device - although there's nothing configured/installed on the device

Side notes

  • It's not possible to make the local sync warnings go away - downloading the cloud settings on the device - besides uploading the settings to the cloud
  • I sent crash dumps to [email protected]

Questions

  • Anything I can do to fix the issue?
  • Is the sync between iPadOS and iOS supported?
  • Are there any settings which are ALWAYS different between those devices
@maxmeyer maxmeyer changed the title Cloud sync between two freshly installed app on iPadOS and iOS produces sync errors / warnings Cloud sync between two freshly installed apps on iPadOS and iOS produces sync errors / warnings Aug 16, 2024
@vshcherb vshcherb added the ! label Aug 20, 2024
@vshcherb vshcherb added this to the 4.9-iOS milestone Aug 20, 2024
@vshcherb
Copy link
Member

There should be no conflict if user installs by default on 2 devices and runs sync . With palette we could use the timestamp if it's the same as in bundled_assets.xml (date was introduced there) then it shouldn't be backed up

@dmpr0
Copy link
Contributor

dmpr0 commented Aug 30, 2024

@DmitryAlexei
Copy link

do we update files when updating app? Files should be updated if the user didn't change them.

@tigrim
Copy link
Contributor

tigrim commented Sep 26, 2024

Technical Plan

Objective

Create a storage system for storing file hashes.

Use Cases for File Changes

  1. Files in the Resources folder are modified.
  2. Users modify files in the Documents folder.

File Replacement Process

  • When a file in the application is replaced, update the storage with the new hash of the file.

Additional Requirements

  • The file containing the hashes should be hidden from the user to prevent modification or deletion.
  • If the hashes are updated, the files will be available for synchronization with the cloud.

@Skalii Skalii linked a pull request Oct 15, 2024 that will close this issue
@tigrim
Copy link
Contributor

tigrim commented Oct 31, 2024

To synchronize, you need to use the bundled_assets.json, which is shared for both iOS and Android. https://github.com/osmandapp/OsmAnd-resources/blob/master/bundled_assets.json

@vshcherb
Copy link
Member

Paritally fixed with bundled.json

@vshcherb
Copy link
Member

  1. Color palettes are fixed
  2. Linked to iOS Cloud sync doesn't restore tracks, favorites correctly #4252

@Zirochkabila
Copy link
Collaborator

Testing 1

4.9.4.4947

  1. Fixed
  2. Waiting for 4252

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants