Repository navigation
ScribbleHub : No result error #2344
Description
Plugin
English: Scribble Hub
Severity
Can't Load Novels
Steps To Reproduce
Just open the plugin
Expected Behavior
Should show results
Actual Behavior
LNReader Version
Beta3
Plugin Version
1.0.2
Android Version
10
Other Details
Webview works, there was recently a maintenance of the site and a new look, i think that broke this
Acknowledgements
- I have searched existing issues and confirmed this is not a duplicate.
- I have written a clear and descriptive title.
- I have updated the app to the latest version 2.0.0.
- I have updated all installed plugins to the latest version.
- I understand that app-specific issues should be reported in the app repository.
Activity
torkita commentedon Jul 29, 2026
Try opening in webview, if the issue persists then it needs a fix
josephsemailacc-dev commentedon Jul 30, 2026
It opens fine in webview. Im having the same problem.
Edit: It started to load a few titles briefly for me, but wouldnt let me find the one I wanted. Only 10 titles will load intermittently. Its still messed up.
torkita commentedon Aug 1, 2026
Are you an contributer here ?
josephsemailacc-dev commentedon Aug 1, 2026
No. I just created an account to give additional help so someone could fix this. It is loading titles now, but the search function for novels is still broken.
joseph-marques commentedon Aug 2, 2026
I'm seeing this too, it seems that the URL for searching in the plugin no longer works, so I've opened #2372 to change it to the seriesfinder URL that you get sent to when using the search box
EDIT: It works OK on the web tester, but running on my real device I see weird behavior where the entries move further down the screen every few seconds
DVD-DAVIDE commentedon Aug 2, 2026
I'm having the same issue. I think that the requests might have been getting blocked by Cloudflare, although the same does not happen with the WebView. Aren't cookies from the WebView supposed to be used while fetching novels as well? After copying my browser cookies to the web tester, the fix from #2372 worked, though.