End of section

This commit is contained in:
validcube 2025-01-27 15:34:25 +07:00
parent 6598db5078
commit 617481f26f
No known key found for this signature in database
GPG Key ID: DBA94253E1D3F267
2 changed files with 26 additions and 3 deletions

View File

@ -14,13 +14,15 @@ In case you encounter any issues while using ReVanced Manager, please refer to t
This indicate that your device doesn't have enough memory to patch the app. Try patching on another device that's have more memory. This indicate that your device doesn't have enough memory to patch the app. Try patching on another device that's have more memory.
In the meantime there's a remedy fix by going to ⚙️ Settings -> Advanced -> toggle "Run Patcher in another process (experimental)" on In the meantime there's a remedy fix by going to `⚙️ Settings -> Advanced -> toggle "Run Patcher in another process (experimental)"` on
- ❗️ Error code `135`, `139` or `1` when patching the app - ❗️ Error code `135`, `139` or `1` when patching the app
Your device is not supported. Refer to the [Prerequisites](0_prerequisites.md) page for supported devices. Your device is not supported. Refer to the [Prerequisites](0_prerequisites.md) page for supported devices.
Alternatively, you can use [ReVanced CLI](https://github.com/revanced/revanced-cli) to patch the app. Alternatively, you can use [ReVanced CLI][ReVanced CLI GitHub]) to patch the app.
[ReVanced CLI GitHub]: https://github.com/revanced/revanced-cli
- 🚫 Non-root install is not possible with the current patches selection - 🚫 Non-root install is not possible with the current patches selection
@ -28,4 +30,16 @@ In case you encounter any issues while using ReVanced Manager, please refer to t
- 🚨 Patched app crashes on launch - 🚨 Patched app crashes on launch
Try selecting the **Default** button when choosing patches, if the patched app still failed, file an issue at [ReVanced Patches](https://github.com/revanced/revanced-patches). Try selecting the **Default** button when choosing patches, if the patched app still failed, file an issue at [ReVanced Patches][ReVanced Patches GitHub].
[ReVanced Patches GitHub]: https://github.com/revanced/revanced-patches
## ⏭️ What's next
The next page will guide you through troubleshooting ReVanced Manager.
You have successfully finished the guide for on how to use ReVanced Manager.
If you wish to review the Table of Content for how to use ReVanced Manager, feel free to do so.
Continue: [💊 ReVanced Manager](/docs/README.md)

View File

@ -10,3 +10,12 @@
3. Submit a pull request to the `dev` branch of the repository and reference issues that your pull request closes in the description of your pull request 3. Submit a pull request to the `dev` branch of the repository and reference issues that your pull request closes in the description of your pull request
4. Our team will review your pull request and provide feedback. Once your pull request is approved, it will be merged into the `dev` branch and will be included in 4. Our team will review your pull request and provide feedback. Once your pull request is approved, it will be merged into the `dev` branch and will be included in
the next release of ReVanced Manager the next release of ReVanced Manager
## ⏭️ What's next
You have successfully finished the guide for developing for ReVanced Manager.
This next section will be verifying the authenticity of ReVanced Manager
which may be relevant for store provider or those who's looking to verify prebuilt librar(ies).
Continue: [✒️ Verification and Authenticity of ReVanced Manager](3_verifying.md)