tryfetch / fetch Goto Github PK

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.

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

Similar to the new functionality on Apple's TV app/Netflix. Should show the next non-accessed show per TV show.

Currently Fetch only supports Put.io but it could be expanded for additional services

• Dropbox
• FTP

Where is the TV app? Is that embedded in this project, or is that somewhere separately?
Thanks for making such a great Put.io client for iOS

Can you update the app to support the new IPHONE X?

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?

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 would love to see support for the iOS Files app in Fetch. Being able to move files from one location to another would be amazing.

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.

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:

This was started before the app was pulled from the app store.

This should replicate what Netflix is doing when watching episodic content. Once the current episode has finished it should auto-play the next until the user stops it.

I can’t seem to get the project to build on High Sierra with Xcode 9. I probably need an older version of Xcode. Could you do another release?

Any chance you could put up build instructions for targeting iOS 12?

Fetch crashes immediately upon launching when running iOS 13.

In the TV shows section the header should display a "Jump to season" section when there is more than once season.

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.

Looks like the timer isn't executing correctly.