-
Notifications
You must be signed in to change notification settings - Fork 2
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
Nyaa 'Stub!' message on compatible apps #18
Comments
Ok so, I took a look at the code and it seems like the extension was designed so it would split torrents with multiple files into separate episodes, but I guess that was never implemented? I just did some testings on my machine with Animetail, and treating an I could either send the changes I made as a fix, or work to do the splitting of entries, but I'm not sure if that would even work. Maybe using something like https://superuser.com/a/1846742 |
Currently Aniyomi do not support torrent, Nyaa only works with Kuukiyomi for now. Need to update torrent lib so it can support Animetail. |
Is it still an issue with Animetail and not with the extension as said before? |
That's weird, I tried running it with the latest Kuukiyomi version as well and it threw the same message. I'm not really an Android developer, but I would imagine the Regardless, I later found out there's already a torrent PR for Aniyomi inspired in Kuukiyomi's implementation, so prob better wait until that is merged before doing anything: |
Source information
Nyaa (Torrent) 14.1
Source language
Multi
Steps to reproduce
Expected behavior
I should be able to see the video entry
Actual behavior
A 'Stub!' toast is triggered
Aniyomi version
0.16.4.3
Android version
14
Other details
Probably related to #9, but even when I tried the last released version of Kuukiyomi I got the same error message. The same also happened with the latest version of Animetail (which supposedly also has torrent support).
My understanding is that Kuukiyomi's torrenting feature was going to get merged into Aniyomi, but I'm not sure what's the status of that currently.
Acknowledgements
The text was updated successfully, but these errors were encountered: