This has already been mentioned previously but the app library won't refresh. The new chapters can nevertheless be read but we cannot see which chapters have been uploaded.
Qidian app not refreshing
This keeps happening all day to me too. And I even get the notification that the new chapters get released but when I enter there isn't any change at all.
Same with me here...
Me too
+1
What version are your app and which platform (IOS/Android)?
Have you tried force closing the app and starting it up again (showing the blue qidian logo page startup)?
joeglens
Android 7.1.1
Qidian App ver. 1.5
I've cleared data+cache and have used the force stop option before starting it up again. It does not show new chapters with the red symbol even though I've never touched em.
Kingfisher Try logging out and logging in back again
- Edited
joeglens No dice, it's red circle on my browser library but no red circle on the app.
EDIT: I haven't force stopped it, just logged off and logged back in
same problems here
UPDATE: I logged off, cleared data+cache, force stopped, and opened it again. Signed in and no dice as well.
- Edited
Kingfisher 1 more step then we go with the nuclear option.
Log-off and clear data+cache then reboot phone, then log in back again
Nuclear Option:
Remove and reinstall the app then reboot phone
- Edited
joeglens Going nuclear.
UPDATE: Nuclear failed, Deleting Qidian folder
UPDATE 2: All my novels are red circle now
To anyone having this issue, please delete Qidian Folder on your phone before doing the nuclear option to see if it fixes it
- Edited
Do NOT delete the Qidian folder. It does not work!
Issue still persists :(
I think there is a major bug on the website that is causing the app to not work properly either. For some reason "the strongest system" is stuck as the latest update since 3 days ago. Hopefully they will fix it.
uninstalled app, removed any related files reinstalled and the problem still persists. deleting folder didnt help as well
@WEBNOVEL_OFFICIAL
tagging in case you didn't notice this :)
Thanks for all your feedback! We've noticed that and our developers were fixing this issue this afternoon.
Well whatever they did it worked :)