app seems to be down
-
Still down on I phone as of 4:05 CST. Seems like a larger outage.
-
Tried my tablet, it works just fine. It is running android 14.
-
Clearing App storage on my Pixel 9 worked for me.
-
@Marius8 update from my end: clearing the data of the app worked.
-
I deleted my cache and data several times and uninstalled a few times, one of them randomly got it to work. Not sure why.
-
Deleted data and I can see stuff. Now in a password reset loop since changing my password on the forum side did nothing to the other side, and I have too many failed attempts now. shrugs
-
I had a failure with the iPhone app (16 Pro running 18.0.1). I deleted the app and info, redownloaded it, logged in and things are fine once more. /knocking on wood…
-
Your issue sounds more unique. Please email support@j-novel.club about it.
-
Deleting the app storage and cache fixed it for me on android 15.
-
@Rahul-Balaggan this worked for iOS for me
-
Clearing data and cache worked for me. Galaxy S21FE, US
-
Android here.
Clear cache didn't work.
Re-Install didn't work.
Clear Data did work.
I did as those steps, so the problem is in data? -
another datapoint.
device is ipad mini 5th gen on 18.1 with the comm error. Force quit and restart did not help. Deleting and reinstalling the app fixed the problem (so far.)
-
I came to find out what was up with this, as the app has been giving me that message for most of the day on my iphone as well. (iPhone 13pro max running iOS 17.6.1). Uninstalling and reinstalling the app did work for me.
Also, the app continued working just fine on my ipad. (iPad Pro running iOS 17.6.1)
Just data points in case they're helpful.
-
Clearing App Cache and Data worked for me (Samsung S21 Ultra).
-
Clearing the cache allowed me to log in and view prepubs. However, all the prepubs I've opened since then are laid out in a single vertically scrolling column with no pagination. I'm on Android.
-
Re-installing worked for me on iphone.
-
Clearing cache did not work
Clearing data did work! -
Hello,
A change has been made that should correct this issue.
Please let us know if it persists.
Thank you
-
This post is deleted!
