Mirrors/tachiyomi-website
2
0
Fork 0
mirror of https://github.com/tachiyomiorg/website.git synced 2024-12-21 07:31:58 +01:00
Code Issues Packages Projects Releases Wiki Activity

Documented more common errors (#830)

Browse Source 
* Documented more common errors

* Fix incorrect icon name

* Correct link to Android 11 section

* Fixed el collapse item initialize

* updated dump crashlogs image

* Actually fix el-collapse

* Addressed PR Review comments

* Changed Android 11 section to 11+

* fix link to migration page
This commit is contained in:
loocool2 2022-01-23 12:02:56 -08:00 committed by GitHub
parent 83799147b3
commit bf513dbca8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 67 additions and 91 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
src/.vuepress/public/assets/guides_dump-crashlogs.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 213 KiB

After

Width:  |  Height:  |  Size: 80 KiB

3
src/help/faq/README.md
View File

@ -17,7 +17,6 @@ No. There is no iOS version, and there are no plans for one. Since iOS and Andro
#### Will Tachiyomi ever be on the Google Play Store?
Google Play's content policy does not allow the APK based extension system to work. The content on some websites will lead to Google taking it down at some point, and Inorichi does not want to have to deal with it as they have stated [before](https://github.com/tachiyomiorg/tachiyomi/issues/1745#issuecomment-441208074).
#### Can Tachiyomi read Light Novels?
No. Tachiyomi is an image parser, not a text parser.
@ -332,7 +331,7 @@ No, unless expressly stated, the internal ID of sources has not changed, so migr
#### What if I uninstall the multisource extension before I install the singular extensions?
See what extension IDs correspond to what extensions [here](https://pastebin.com/raw/QX2scdRT).
## Android 11
## Android 11+
### What changed in Android 11?
In Android 11, Google began forcing users to use [Scoped Storage](https://developer.android.com/about/versions/11/privacy/storage), which was introduced in Android 5.0 Lollipop, but Google only began forcing developers to use it on Android 11. Some OEMs seem to better implement Scoped Storage than others, with some users not running into any issues while users using other phone brands have multitudes of problems.

155
src/help/guides/troubleshooting.md
View File

@ -8,46 +8,46 @@ lang: en-US
This page is for when you encounter a problem with a source or the app.
### What are some common errors?
::: c-warning
If error-specific instructions didn't help or your error isn't on the list, go through [Diagnosis](#diagnosis).
:::
### What are some common issues?
:::: el-collapse
::: el-collapse-item title="Java.lang Exception: Challenge not found"
Often **Java.lang Exception: Challenge not found** will be resolved by force-quitting and reopening **Tachiyomi**.
:::
::: el-collapse-item title="Java.lang Exception: Failed to bypass Cloudflare"
**Java.lang Exception: Failed to bypass Cloudflare** means that the source you selected has [Cloudflare](#solving-the-cloudflare-issue) protection on, refer to the [Cloudflare](#solving-the-cloudflare-issue) guide to fix it.
:::
::: el-collapse-item title="Loader not implemented"
**Loader not implemented** means that the respective extension for the manga is not installed. To fix this, install the extension for the manga. If it still doesn't work, uninstall, then reinstall the extension again.
**Java.lang.Exception: Failed to bypass Cloudflare** means that the source you selected has [Cloudflare](#solving-cloudflare-issues) protection on, refer to the [Cloudflare](#solving-cloudflare-issues) guide to fix it. If the solutions provided do not fix the issue, the source has likely raised the Cloudflare protection level high enough that Tachiyomi is not able to access the site.
:::
::: el-collapse-item title="HTTP error 403"
Possible reasons for **HTTP error 403**:
- The source you selected has [Cloudflare](#solving-the-cloudflare-issue) protection on, refer to the [Cloudflare](#solving-the-cloudflare-issue) guide to fix it.
- The source you selected has [Cloudflare](#solving-cloudflare-issues) protection on, refer to the [Cloudflare](#solving-cloudflare-issues) guide to fix it.
- The source is down, removed the manga, or banned your IP. Open <NavigationText item="webview"/> to check if this is the case.
:::
::: el-collapse-item title="HTTP error 404"
**HTTP error 404** probably means that the source is down or removed the manga. Open <NavigationText item="webview"/> to check if this is the case.
**HTTP error 404** probably means that the source is down or removed the manga. Open <NavigationText item="webview"/> to check if this is the case. [Migrate](/source-migration/#migrating-on-stable-preview) to a different source for this manga if you'd like.
:::
::: el-collapse-item title="HTTP error 429 (Too Many Requests)"
**HTTP error 429** or **Too Many Requests** means that the source banned your IP address (in most cases, it's temporary). We suggest [migrating](./source-migration.md) part of your manga to another source to reduce the number of requests to the source.
**HTTP error 429** or **Too Many Requests** means that the source banned your IP address (in most cases, it's temporary) because you could be downloading or reading too fast. We suggest [reporting](https://github.com/tachiyomiorg/tachiyomi-extensions/issues/new/choose) the issue so that a rate limit can be added to prevent IP bans in the future.
:::
::: el-collapse-item title="HTTP error 5xx"
**HTTP error 5xx** like **500, 502** and others are server errors, and the source you are trying to access has problems on their side. Open the source in <NavigationText item="webview"/> and check if the site is down.
**HTTP error 5xx** like **500, 502** and others are server-side errors, and the source you are trying to access has problems on their side. Open the source in <NavigationText item="webview"/> and check if the site is down.
:::
::: el-collapse-item title="Unable to resolve host / Connection failed"
Errors like **Unable to resolve host** or **Connection failed** mean that something prevents your connection to the site.
::: el-collapse-item title="HTTP error 1006"
**HTTP error 1006** means that the source has banned your IP address (in most cases, it's temporary).
:::
::: el-collapse-item title="HTTP error 1020"
**HTTP error 1020** means that you have violated a firewall rule the site owner has put up. This usually means that the site owner has raised the Cloudflare protection level or that the site owner is blocking IPs outside their country.
:::
::: el-collapse-item title="Unable to resolve host / Connection failed / Failed to connect to / timeout / connection reset"
Errors like **Unable to resolve host**, **Connection failed**, **Failed to connect to**, **timeout**, **connection reset** mean that something is preventing you from connecting to the source.
Possible reasons include:
- Your internet connection is not good enough to connect.
- The app does not have access to the internet.
- Your ISP has blocked the site.
- The site is down.
Try using different internet connection (switch to Wi-Fi, mobile data or a VPN). Try to enable <NavigationText item="more"/> → <NavigationText item="settings"/> → <NavigationText item="settings_advanced"/> → **DNS over HTTPS**.
Try the following solutions to fix this issue:
- Enable <NavigationText item="more"/> → <NavigationText item="settings"/> → <NavigationText item="settings_advanced"/> → **DNS over HTTPS**.
- Use a different internet connection (switch to Wi-Fi, a different Wi-Fi network, mobile data or a VPN).
- Reboot your router.
:::
::: el-collapse-item title="java.security.cert.CertPathValidatorException / Chain validation failed"
**java.security.cert.CertPathValidatorException** or **Chain validation failed** means there is a problem with validating source's sertificate.
@ -55,83 +55,48 @@ Try using different internet connection (switch to Wi-Fi, mobile data or a VPN).
- Check if the site's certificate has expired. Use an online service for checking SSL certificates. If the certificate has expired, wait while the site owner to renew it.
- Ensure that you have the right date and time set on your phone.
- Try <NavigationText item="more"/> → <NavigationText item="settings"/> → <NavigationText item="settings_advanced"/> → **Clear cache** and **Clear cookies**.
- Try using a different internet connection (switch to Wi-Fi, mobile data or a VPN).
- Try using a different internet connection (switch to Wi-Fi, a different Wi-Fi network, mobile data or a VPN).
- Try restarting the device.
:::
::: el-collapse-item title="App not installed"
You may encounter **App not installed** if you're installing an official build over an existing **F-Droid** build due to differing signatures.
Backup your data, uninstall the app, then restore the data in the fresh install.
Refer to [this](#unable-to-install-the-app-or-extensions) section.
:::
::: el-collapse-item title="Attempt to invoke virtual method 'com.hippo.unifile..."
The **Attempt to invoke virtual method' com.hippo.unifile...** error can be caused by various reasons, but they all have to do with storage.
- Most commonly, it is caused by full storage. Check to see if your device or SD Card is full.
- Check if **Tachiyomi** has access to the SD card. You can enable it in the android settings for app permissions.
- Check if **Tachiyomi** has access to the SD card. You can enable it in Android settings for app permissions.
- If you're downloading and this error pops up, that means the app might not be able to access the folder you're trying to download to. This may be because the folder is corrupted or does not exist. Use a file manager to check that the folder(s) exist and every folder in the sequence is available and accessible.
- The drive you're writing to is corrupted. Check using a file manager to see if it is accessible.
:::
::: el-collapse-item title="Cannot Access SD Card"
**Cannot Access SD Card** error is typically caused by having a file or folder name that is too long. Android's file manager does not support filenames longer than 255 characters. If you know the file or folder name that is the culprit, you can connect your SD card to your computer and shorten it. Otherwise, delete the Tachiyomi downloads folder off of the SD Card.
The **Cannot Access SD Card** error can sometimes be fixed by changing the location of your downloads to somewhere else and back to the SD card, then restarting the app.
Having a file or folder name that is too long can also cause this issue. Android's file manager does not support filenames longer than 255 characters. If you know the file or folder name that is the culprit, you can connect your SD card to your computer and shorten it. Otherwise, delete the Tachiyomi downloads folder off of the SD Card.
:::
::: el-collapse-item title="Storage issues with Android 11"
Following the introduction of [Scoped Storage](https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/) in **Android 11**, your library could load slowly, or the app is unable to delete chapters automatically.
One way to fix this is by executing an [ADB](https://www.xda-developers.com/quickly-install-adb/) command on a computer to opt-out the app for the new storage changes.
**How to run ADB**
ADB is a small tool bundled in the Android SDK as part of the "Platform Tools."
1. [Download the SDK Platform Tools](https://developer.android.com/studio/releases/platform-tools.html) for Windows, Mac, or Linux
2. Extract the ZIP file somewhere easily accessible (like `C:\platform-tools`)
You will need to enable "USB Debugging/Android Debugging" on your phone next:
* If you use a custom ROM or aren't able to enable Developer options, try googling how to enable Developer options on your specific device
1. Open **Settings**
2. (Only on Android 8.X) Scroll down/Select to **System**
3. Select **About phone**
4. Quickly tap **Build number** 7 times
5. You will see a message appear that says, "**You are now a developer**."
6. Now go back, and you'll see **Developer options** listed
7. Scroll until you find **USB debugging/Android debugging**
8. Toggle the switch to enable it
With platform-tools downloaded and USB debugging enabled, you can now follow the following steps:
1. Connect your Android device to the computer with a USB cable
2. Make sure to allow "USB debugging/Android debugging" when a pop-up appears
3. Open the **platform-tools** folder on your computer
4. Shift+Right click and select **Open command prompt here** or **Open PowerShell window here**
5. Type `.\adb devices` and hit Enter
6. You should see an entry with your device(s)
7. Now, enter the following ADB command:
**ADB command**
`.\adb shell cmd appops set eu.kanade.tachiyomi android:legacy_storage allow`
If you're using Preview, or a Fork, replace `eu.kanade.tachiyomi` with the other app's ID.
* **Tachiyomi Preview** → `eu.kanade.tachiyomi.debug`
* **TachiyomiAZ** → `eu.kanade.tachiyomi.az`
* **TachiyomiJ2K** → `eu.kanade.tachiyomi.j2k`
* **TachiyomiSY** → `eu.kanade.tachiyomi.sy`
* **Neko** → `tachiyomi.mangadex`
***Please note that the command will not show any output if it is successful.***
::: el-collapse-item title="Storage issues with Android 11+"
See [this](/help/faq/#android-11) section of the FAQ to learn how Scoped Storage affects Tachiyomi in Android 11+ and how to fix it.
:::
::: el-collapse-item title="Slow loading"
<ElAlert type="info" title="Disclaimer" description="Tachiyomi is not hosting any content, we are not affiliated with or responsible for any source that is; slow, down, missing chapters, or has subpar image quality." show-icon :closable="false"></ElAlert>
If any sources are slow, it is likely due to the site being slow, your internet being slow, or a ratelimit applied to the source to reduce load or IP bans.
:::
::: el-collapse-item title="Reading is laggy"
This is usually due to the images in the chapters being too long or large for the reader to handle. If you turn have **32-bit color** on, try turning it off under <NavigationText item="more"/> → <NavigationText item="settings"/> → <NavigationText item="settings_reader"/>. This helps sometimes to free up some RAM being used. To eliminate this issue, find a different source that cuts the chapter into more pieces or downscales the images.
:::
::::
::: c-warning
If error-specific instructions didn't help or your error isn't on the list, go through [Diagnosis](#diagnosis).
:::
## Diagnosis
* Verify your extensions are up to date (<NavigationText item="browse"/> → **Extensions**, make sure no extensions have an **Update** button).
* Check if **Tachiyomi** has an update (<NavigationText item="more"/> → <NavigationText item="about"/> then tap **Check for updates**).
* Manually refresh the manga you are having issues with by dragging down.
* Check other manga from the source.
* Verify that [WebView](#update-webview) is updated.
* Try opening the manga in <NavigationText item="webview"/>. If there is a [Cloudflare](#solving-the-cloudflare-issue) protection, wait for it to load. If there is a [CAPTCHA](#solving-the-cloudflare-issue), solve it and see if it helped.
* Try opening the manga in <NavigationText item="webview"/>. If there is a [Cloudflare](#solving-cloudflare-issues) protection, wait for it to load. If there is a [CAPTCHA](#solving-cloudflare-issues), solve it and see if it helped.
* Change your internet connection (*switch to Wi-Fi, mobile data or a VPN, use a "What's my IP" site to confirm your IP has changed*), then try again.
* Ask other users to try the action that gives you the error.
* Check if the source is either down, or is having issues in a browser.
@ -145,23 +110,23 @@ If you're using Preview, or a Fork, replace `eu.kanade.tachiyomi` with the other
* Force close **Tachiyomi** and reopen it.
::: c-tip
The Preview version may have already fixed your issue. Just wait for a new Stable release.
An extension update may fix your issue. Wait or check for an extension update if you have not already. There are no ETAs for updates.
:::
If any of these solutions help, go to [it only happens to me](#it-only-happens-to-me).
If it's not just you, go to [everyone is having this problem](#everyone-is-having-this-problem).
If it is not just you, go to [everyone is having this problem](#everyone-is-having-this-problem).
If none of these solutions help, try asking in our [Discord Server](https://discord.gg/tachiyomi). State your app version and the source, manga, and chapter with the problem.
If none of these solutions help, try asking in our [Discord Server](https://discord.gg/tachiyomi). Check **#status-updates** first to see if your issue is known. State your app version and the source, manga, and chapter with the problem if it is not listed.
### It only happens to me
You may be getting a [Cloudflare](#solving-the-cloudflare-issue) protection, may have been IP-banned, or encountered some other counter-measure that website owners deploy against programs like **Tachiyomi**. If that is the case, there is probably nothing that **Tachiyomi** can do to solve it. Some of them (like [Cloudflare](#solving-the-cloudflare-issue)) have to be manually solved, and some are temporary (IP bans).
You may be getting a [Cloudflare](#solving-the-cloudflare-issue) protection, may have been IP-banned, or encountered some other counter-measure that website owners deploy against programs like **Tachiyomi**. If that is the case, there is probably nothing that **Tachiyomi** can do to solve it. Some of them (like [Cloudflare](#solving-cloudflare-issues)) have to be manually solved, and some are temporary (IP bans).
**Workarounds that can the lower chance of an issue happening again:**
* Don't use downloads with the source.
* Have less manga in your library from the source.
::: c-warning
The above are very imprecise and fuzzy rules because each site has its non-public limits and triggers.
The above are imprecise and fuzzy rules because each site has its non-public limits and triggers.
:::
### Everyone is having this problem
@ -172,9 +137,9 @@ If the site is reachable and fully functional, there may be an issue with the ex
If the site is not reachable or has issues, all you can do is wait for the site to become functional again.
## Solving the Cloudflare issue
## Solving Cloudflare issues
**Please note that WebView is not the same as using your browser.**
**Note that WebView is not the same as using your browser.**
You must solve the **Cloudflare** issue in **WebView**.
@ -189,7 +154,7 @@ You must solve the **Cloudflare** issue in **WebView**.
1. Once done, press the X at the top left to return.
:::
## Bypassing Cloudflare looping
### Bypassing Cloudflare looping
Some sources may have more advanced **Cloudflare** protection, that results in infinite loading in **WebView** when trying to bypass **Cloudflare** using the solution above. If you are facing this issue, try the following steps:
@ -206,21 +171,33 @@ Some sources may have more advanced **Cloudflare** protection, that results in i
## Update WebView
To update **WebView**, you need to find what **WebView implementation** is used on your device. In general, default implementation depends on the Android version as follows:
* Android 10.0 and higher - [Android System WebView](https://play.google.com/store/apps/details?id=com.google.android.webview).
* Android 10.0 and up - [Android System WebView](https://play.google.com/store/apps/details?id=com.google.android.webview).
* Android from 7.0 to 9.0 - [Google Chrome](https://play.google.com/store/apps/details?id=com.android.chrome).
* Android 6.0.1 and lower - [Android System WebView](https://play.google.com/store/apps/details?id=com.google.android.webview).
* Android 6.0.1 and below - [Android System WebView](https://play.google.com/store/apps/details?id=com.google.android.webview).
::: c-tip
Users on Android 7.0 and up can also see and change **WebView implementation** in [Developer Options](https://developer.android.com/studio/debug/dev-options).
:::
::: c-warning
Non-standard implementations like Firefox can lead to **Tachiyomi** not working correctly or, in the worst-case crash. We recommend to set **WebView implementation** to [Android System WebView](https://play.google.com/store/apps/details?id=com.google.android.webview) or [Google Chrome](https://play.google.com/store/apps/details?id=com.android.chrome).
Non-standard implementations like Firefox can lead to **Tachiyomi** not working correctly or, in the worst-case, crash. We recommend to setting your **WebView implementation** to [Android System WebView](https://play.google.com/store/apps/details?id=com.google.android.webview) or [Google Chrome](https://play.google.com/store/apps/details?id=com.android.chrome).
:::
## Unable to install the app or extensions
Try installing [Split APK Installer](https://play.google.com/store/apps/details?id=com.aefyr.sai) from the Google Play Store, then use it to try and install the affected APK. Split APK Installer will tell you why the APK is uninstallable, or it will install the APK for you.
Try installing [Split APK Installer](https://play.google.com/store/apps/details?id=com.aefyr.sai) from the Google Play Store, then use it to try and install the affected APK. Split APK Installer will tell you why the APK is uninstallable, or it will install the APK for you. Some common errors are listed below.
:::: el-collapse
::: el-collapse-item title="INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package eu.kanade.tachiyomi signatures do not match the previously installed version; ignoring!"
If Split APK Installer outputs the above error when attempting to install the APK, you are likely installing a official build over an existing **F-Droid** build. The **F-Droid** build has a different signature than the official build, so you must backup your data, uninstall the app, then restore the data in a fresh install.
:::
::: el-collapse-item title="DISPLAY_NAME column is null"
If Split APK Installer outputs "DISPLAY_NAME column is null", the APK you have downloaded is corrupted. Some users experience this error multiple times after redownloading the APK, so keep redownloading the APK until it installs correctly.
:::
::: el-collapse-item title="INSTALL_FAILED_NO_MATCHING_ABIS"
If Split APK Installer outputs "INSTALL_FAILED_NO_MATCHING_ABIS", the APK you have downloaded is the wrong one for your CPU architecture. Download the correct one or download the universal APK if you are not aware which CPU architecture your device uses.
:::
::::
## Getting Logcats and Crash Logs
@ -232,4 +209,4 @@ To dump crash logs following an app crash, go to <NavigationText item="more"/>
</figure>
:::
To get device logs if the app is not behaving as expected, record the device logs using a [Logcat Reader](https://play.google.com/store/apps/details?id=com.dp.logcatapp).
To get device logs if the app is not behaving as expected, record device logs using a [Logcat Reader](https://play.google.com/store/apps/details?id=com.dp.logcatapp).