After fresh install, I was unable to login and it seems some changes either on put.io API or elsewhere. The following changes allowed me to progress, perhaps there is a better solution. I'm not too familiar with the oauth flow and used this as quickest route to be able to login.

I pulled down the latest project files. Installed xcode 8.3.3. Successfully ran ./prepare with no errors. Launch Xcode, select a device (iPhone 7 plus) and click run and Xcode reports a build error that it cannot find Alamofire.

See the screenshot:

Using the latest release version on iOS 11 fully patched to 11.2.1 on both iPhone X and IPad Pro.

After a while Fetch gets into a state where it crashes on launch. It launches but before it can paint the main window it immediately quits. I’ve seen this behavior on both of my iOS devices. Seems like it happens around the same time. Starts happening on one and then the other. The only way I can get it to work again is to remove it and reinstall it.

I'm constantly hitting #22 because days after I build the application something goes strange with provisioning. I've lost access to local downloaded content multiple times while away from computer and it's a little annoying.

As a solution, it would be great if downloaded content in fetch wasn't locked into fetch and the application allowed you to consume the content with other apps, or view downloaded files in the files app.

This pull request enables consuming the downloaded files from the files app:

The side effect, you can extra these files on macOS via iTunes too:

This happens by enabling UIFileSharingEnabled and LSSupportsOpeningDocumentsInPlace:

UIFileSharingEnabled

In iOS 11 and later, if both this key and the LSSupportsOpeningDocumentsInPlace key are YES, the local file provider grants access to all the documents in the app’s Documents directory. These documents appear in the Files app, and in a Document Browser. Users can open and edit these document in place.

The downside is that it does show the realm store files in Files.app as they are stored in the documents folder. Perhaps it would make sense to move these files outside of Documents or limit the files exported in some way but I am not aware of a trivial way to do this so I left it.

Using the latest release version. When selecting a file to download for offline viewing, there is no indicator the file is actively downloading. Normally there is a little red dot on the "...more" button with the # of files downloading. After adding several more files, the indicator is showing up. So maybe there is a bug?

This was caused by the swift3 conversion. This is a subtle change in swift3, see https://stackoverflow.com/a/39537558/158525 Explicitly unwrapping the url fixes the issue.

Just needed to set the delegate so that func playerViewController(playerViewController: AVPlayerViewController, restoreUserInterfaceForPictureInPictureStopWithCompletionHandler completionHandler: (Bool) -> Void) is handled.

This PR adds a "share" button when swiping a downloaded file in the downloads area. This lets you share a downloaded file over airdrop and such.

Can't get past the authorisation screen. Receive error:

Warning:

file_get_contents(https://api.put.io/v2/oauth2/access_token?client_id=2023&client_secret=xn0ul0zflut87yz0tuw1&grant_type=authorization_code&redirect_uri=http://getfetchapp.com/authenticate&code=47NEIOTW): failed to open stream: Connection timed out in /home/steve228uk/webapps/fetchapp/authenticate/index.php on line 10

Warning: Cannot modify header information - headers already sent by (output started at /home/steve228uk/webapps/fetchapp/authenticate/index.php:10) in /home/steve228uk/webapps/fetchapp/authenticate/index.php on line 15

When Fetch matches files to metadata it can crash if your movie has the date at the beginning of the filename. Create a folder and movie with the following title and Downpour will throw an error:

1984.1984.720p.BluRay.H264.AAC.mp4

The error is happening in Downpour.swift line 151:

} else if year != nil {
                let endIndex = rawString.index(rawString.range(of: year!)!.lowerBound, offsetBy: -1)
                return rawString[rawString.startIndex...endIndex].cleanedString
            }

I think the index is going out of range due to the offset, but I could be wrong. Its been a longtime since I've written code.

When you download a video file in fetch that doesn’t have the .mp4 file extension (such as .mkv), a generic error message is produced once the file is downloaded. The error message says that the device may have ran out of storage. It seems the download is actually successful and works.

I’ll try to take a look into this myself, just posting here for tracking purposes. Haven’t digged into it yet. I think the code is assuming mp4 extension and then checking for the file locally that doesn’t match the name.

Fetch could provide a file provider using the iOS APIs, this would allow seeing files from put.io inside other applications such as the Apple Files app.