Skip to content
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.

Commit

Permalink
Merge pull request #839 from owncloud/add-available-offline-glitch-to…
Browse files Browse the repository at this point in the history
…-faq

Document glitch with multiple edits in offline session
  • Loading branch information
settermjd committed Feb 9, 2017
2 parents fa343bb + 590673b commit b08ddff
Showing 1 changed file with 21 additions and 6 deletions.
27 changes: 21 additions & 6 deletions user_manual/ios_faq.rst
Expand Up @@ -2,14 +2,29 @@
iOS App FAQ
===========

**Issue:**
Enabling "Background Instant Upload" requires the Owncloud client to have access to location services
-----------------------------------------------------------------------------------------------------

Enabling the "Background Instant Upload" feature requires that the Owncloud client have access to location services.
In order to check for new images to be uploaded, the ownCloud iOS application
uses location services to wake the application in background.
If new images are ready to be uploaded, they are then uploaded.

**Resolution:**
.. NOTE::
The iOS App don't send location information to any server.

The ownCloud iOS App uses the location to wake up the app in background in order to check if there is any new image to be uploaded, if so, images are uploaded.
See https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/LocationAwarenessPG/CoreLocation/CoreLocation.html for more information.

The iOS App don't send location information to any server.
Files marked "available offline" aren't available offline after editing
-----------------------------------------------------------------------

See https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/LocationAwarenessPG/CoreLocation/CoreLocation.html for more information.
Currently, there is a limitation in the “Available Offline” feature in the iOS
client application.
A file *is* editable offline.
However, after the first edit, if the file is closed it goes into a *"ready to
be synced"* state.
When this happens, until it is synced, only the old version will be available.
The reason why is that each change is, internally, queued separately for syncing
with the remote ownCloud server.
And, these changes are not merged locally until the remote sync finishes.
What’s more, if a file is edited multiple times, when it is eventually synced
with the remote server, conflicts in the document may also occur.

0 comments on commit b08ddff

Please sign in to comment.