Hi @all,

My wife’s SeafilePro App freezes after it auto uploads 2 pictures. Every time, it is reproducible. That is not very fun with 240 pictures to go. iPhone 7 - iOS 11.2.1 SeafilePro 2.7.1 App

Strangely my iPhone SE with the same software versions works.

Please help :)

Thanks in advance!

After uploading photos from my iPhone (v.2.5.7) into an encrypted library, some (~30%) of these pictures cannot be opened, neither via Sync Client on Mac nor via Web GUI (server v. 6.0.7)

The script to check for corrupted libraries on the server runs without errors and considers all libraries as ok. How could I further debug? Thanks a lot in advance!

For iOS 11, Apple has (for the first time!) announced that it is going to have a new "Files" app that lets users place their files centrally and open the same file with different apps, without needing to go via the "share" menu. File Sync Apps like Dropbox, Box, OneDrive will be supported from the get-go.

I think it would be great if the Seafile iOS app can serve as a FileProvider; see here: developer.apple.com/documentation/fileprovider for details. Maybe you can investigate this option for iOS 11.

Using the seafilePro App 1.0 on my iPad2 and iPhone5. Everything works fine but I can't upload any file. If I add a photo, an attachment, whatever, the file is listed inside the choosen library, but the status is "Waiting for upload..."

I restartet everything, App, iPhone/iPad, re-added the account, restarted the server, but nothing. The status is still the same "Waiting for upload...".

Version: 1.9.9 iPhone 5 iOS 7.1.1.

I tried to upload photos my seafile private server. The library is connected with https and a valid certificate.

As you can see from the following image. The upload does not start:

Version info:

iPhone 5 - iOS 8.1 Seafile Server (self-hosted, CommunityEdition) 3.1.7 (x64 Linux)

Description:

• "Auto Camera Upload" is always enabled in the settings of the iOS App
• clicking on "Upload Destination" doesn't show a popup or does anything at all

Steps taken:

• reinstalling the iOS app & recreate account(s) -> no change
• restarting the phone -> no change
• tested on different hardware -> working on iPad Air with iOS 8.1
• updated server version from 3.1.5 to 3.1.7 -> no change
• checked/removed/re-added permissions to access the photo library
• tried all of the above via Edge, UMTS & Wifi -> no changes

please advice, happy to help.

regards,

chris

I’m using SeafilePro on my linux server, my iOS client was fully functional until after I updated to the last version.. when I try to upload photos, the process freezes after few seconds of uploading. You can further see that in this video which I captured: https://goo.gl/wVST83

On my iphone5 (iOS 8.1.2) image auto sync in seafile 1.9.3 does not detect automatically when new photos are taken. I have to refresh the library screen in the app manually to start the upload of new photos.

how to re-produce: open seafile client, open any library, on top right corner, click +, the app will crash and went back to home screen.

version: 1.7 iOS 8.0

I am using the IOS client 2.5.9 with a 6.0.7 server and have the following problem: I can browse all Libraries and folders without issue, but when I select a file, it starts downloading, then stays on the download screen instead of displaying the file.

Like this, the client is kind of useless.

Using iOS 7, I observed the following issues (which are not present using iOS 8 or 9):

• swipe any item in the library, then select "more" or "delete" -> nothing happens
• try to upload a photo -> infinitely waiting for upload

I know iOS 7 is fairly outdated. However, some devices cannot be upgraded, and the seafile client app is available for these, but mostly unusable.

Version: 2.9.18

Background upload works only if app is open In some cases, even if the application is open, synchronization may hang. Unloading and opening the app again helps.

1. Had seafile configured with 1 account (CE Server). "Files" app shows Seafile with this server ip. Works fine.
2. Added a new account to Seafile (Pro Server this time). Removed old account.
3. "Files" still shows the old server with old ip, not browsable. Tried restaring Seafile app, Files app and phone but no luck.

Only solution found was to uninstall the Seafile app and install it again, and readd account again.

Hello,

I am using the iOS App to automaticly sync photos to my seafile server. After activating the feature, all photos was uplaoded successfully to my server. But, I keep having the problem that all photos are uploaded again sometimes. This is really annoying, because on the one hand the date of the photo is no longer correct (see also #317) and on the other hand a lot of pointless traffic is generated every time (More than 1000 photos with about 3 MB each).

It would be great if the automatic photo upload would be revised to avoid such problems.

By the way, the photos on the server have not been changed in the meantime. Maybe you can tell me what attribute is used by the app to determine if a photo already exists on the server? Maybe the problem can be better isolated this way.

Thanks, Frank

Integrating the SEAFile ActivityViewController in my app, I am trying to properly handle the case where the user hits the "Cancel" button in the SEAFile VC - so that I can unwind any preparation done prior to sharing.

The following code is used:

    // Make the activityViewContoller which shows the share-view
    let shareViewController = UIActivityViewController(activityItems: filesToShare, applicationActivities: nil)

    // Show the share-view
    self.present(shareViewController, animated: true, completion: {
    // print("Activity finished...")
    })
    shareViewController.completionWithItemsHandler = { activity, completed, items, error in
        if !completed {
            // handle task not completed, put the original file back in place ..
            let _ = FileManager.default.secureMoveItem(at: destinationFileURL, to: sourceFileURL)
                        
            print("Restored database file from: " + destinationFileURL.absoluteString + " back to: " + sourceFileURL.absoluteString)
            return
        }
        else {
            if (activity != nil) {
                self.createEmptyDB()
            }
        }
                
        self.updateUI()
    }
}

The trouble is, "completed" is always true - even if the user cancels, and activity is always "com.seafile.seafilePro.SeafAction", so it cannot be checked for .. meaning that no matter if the user cancels the SEAFile upload, the "self.createEmptyDB()" function is called.

Seems to me this is a bug in SEAFile ActivityView - it should not return an activity if the user cancels, but I am not sure. Can other devs check this code and see if I'm missing something - otherwise, seems like a bug in SEAFile.