-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Torrent intents not recognized #57
Comments
Same issue here, but sometimes it works though. Always works when using add function in app. Might be a chrome/Android based problem? I'm using cm N based ROM. |
If sometimes it worked, most probably it was the website you were downloading the torrent from didn't set the MIME type correctly. Gearshift has nothing to do with this. |
If you add a torrent from IPTorrents it always gives error. I use Firefox for Android. The same torrent but saved locally and added through Add Torrent works fine always. |
@subiol |
I really like your solution to managing destination folders. I would be very happy to use the app, but unfortunately I faced the problem discussed above. It seems to me that there is a problem with intent-based file sharing introduced at SDK24. The intent sharing operation does not work, but the same .torrent file can be opened manually without problems. |
When I add a new torrent from another another program (f.e. clicking a link in a browser), if it is a magnet link gearshift adds the new torrent correctly, but if it is a .torrent file it fails.
If I save the same .torrent file in the phone and use the add torrent option, then select the .torrent file, it gets added correctly. Since the same .torrent file works when added manually from local memory, but not when coming from another app, that is why I suspect the problem is in how gearshift handles .torrent intents.
The text was updated successfully, but these errors were encountered: