When the user deletes the file locally with the enabled icloud happens this:
1. the file is moved to the local .Trash dir
2. the LocalDirectoryMonitor send event to delete the file from the iCloud
3. the SynchronizationFileWriter trash the remote file using the system API `try fileManager.trashItem`
4. the file is moved to the devices trash
5. the icloud sends the update to the metadataQery's `queryDidUpdate` with the updated state. This update is tricky - it calls the method twice: on the first call the deleted file appears in the updated list (`userInfo[NSMetadataQueryUpdateChangedItemsKey]`) and on the second call the deleted file appears in the deleted list (`userInfo[NSMetadataQueryUpdateRemovedItemsKey]`). There is no way to disable this behaviour.
At that point the bug can happens: the 1st `update` (that contains the file in the deleted list) call can triggers the file recreation because the synchroisztion starts to process the event and make an attempt to recreate the file but it is already deleted.
The fix is: skip missed file during the `Update` event. The case when the missed file is in the updated in undefined and should be skipped by checking the file existence.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
1. for now the structure is SheetStyle.Global/PlacePage/Font/TestColor...
2. the styles are used by assessing the property
before:
lineView.setStyleAndApply("Divider")
headerTitleLabel.setStyleAndApply("semibold18:blackPrimaryText")
after:
lineView.setStyleAndApply(.global(.divider))
headerTitleLabel.setFontStyle(.semibold18, color: .blackPrimary)
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
Also the issue for the PP VC in `traitCollectionDidChange` was fixed. It is needed to prevent PP reloading when the alert is presented over the screen. It happens because the new trait updates can be passed to the `traitCollectionDidChange` method on the every layout update and it cause the steps and layout recalculations. The PP should be reloaded only when the vertical size class is changed.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
1. setElevationActivePoint is changed to work withe the CLLocationCoordinate2D that allows to pass the selected point to the core and show the blue mark on the track in the correct place
2. initWithElevationInfo is removed from the PlacePagePreviewData because the elevation profile is a part of track now and the PP header is configured in the core
3. ElevationHeightPoint stores the coordinates for easily track marks creation
4. add PlacePageTrackData to the PlacePageDate
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
This refactoring allows to split the data for the PP on 2 parts:
1. TrackRecordingInfo (dist, dur, acend, descend etc)
2. ElecationProfileData (only the points to draw)
Because the PP should be created only with the 1st one for the TrackRecordings (will be implemented later) and the PP shoul display all the info without the chart.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
The separators that was created in the storyboards and xibs is very hard to find/select/edit/change width and color. This is why they should be configured and added programmatically.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
