Update api-exception documentation

This commit is contained in:
2022-11-29 00:52:27 +08:00
parent a03a111a4f
commit 864a392698
2 changed files with 68 additions and 0 deletions

View File

@@ -734,6 +734,24 @@ Under normal circumstances, this error basically does not occur. After eliminati
::: danger loggerE ::: danger loggerE
You cannot inject module resources into yourself
:::
**Abnormal**
Use `injectModuleAppResources` in the (Xposed) Host environment (the Module App's own Xposed Environment) to inject the Module App's own resources into itself.
**solution**
Since the Module App itself can also be Hooked by itself, you cannot inject yourself into the Module App itself (you cannot recurse its own resources).
If you must obtain the resources of the Module App itself, please use it directly without any other operations.
###### exception
::: danger loggerE
Activity Proxy initialization failed because got an Exception Activity Proxy initialization failed because got an Exception
::: :::
@@ -839,6 +857,24 @@ registerModuleAppActivities(proxy = "com.demo.test.TestActivity")
Please make sure that the `Activity` name you fill in really and effectively exists in the Host App, and the target `Class` extends `Activity`. Please make sure that the `Activity` name you fill in really and effectively exists in the Host App, and the target `Class` extends `Activity`.
###### exception
::: danger loggerE
You cannot register Activity Proxy into yourself
:::
**Abnormal**
Use `registerModuleAppActivities` to inject the Module App's own `Activity` into itself in the (Xposed) Host environment (the Module App's own Xposed Environment).
**solution**
Since the Module App itself can also be Hooked by itself, you cannot inject yourself into the Module App itself (you cannot recurse its own resources).
If you must obtain the resources of the Module App itself, please use it directly without any other operations.
## Blocking Exceptions ## Blocking Exceptions
> These exceptions will directly cause the app to stop running (FC), at the same time print `E` level logs on the console, and also cause the Hook process to "die". > These exceptions will directly cause the app to stop running (FC), at the same time print `E` level logs on the console, and also cause the Hook process to "die".

View File

@@ -708,6 +708,22 @@ Failed to inject module resources into \[**RESOURCES**\]
::: danger loggerE ::: danger loggerE
You cannot inject module resources into yourself
:::
**异常原因**
在 (Xposed) 宿主环境 (模块自身的 Xposed 环境) 中使用 `injectModuleAppResources` 将模块自身的资源注入自身。
**解决方案**
由于模块自身也可以被自身 Hook但你并不可以在模块自身注入自己 (不能递归自身的资源),若你一定要获取模块自身的资源,请直接使用即可,无需任何其它操作。
###### exception
::: danger loggerE
Activity Proxy initialization failed because got an Exception Activity Proxy initialization failed because got an Exception
::: :::
@@ -804,6 +820,22 @@ registerModuleAppActivities(proxy = "com.demo.test.TestActivity")
请确认你填入的 `Activity` 名称真实有效地存在于宿主中,且目标 `Class` 继承于 `Activity` 请确认你填入的 `Activity` 名称真实有效地存在于宿主中,且目标 `Class` 继承于 `Activity`
###### exception
::: danger loggerE
You cannot register Activity Proxy into yourself
:::
**异常原因**
在 (Xposed) 宿主环境 (模块自身的 Xposed 环境) 中使用 `registerModuleAppActivities` 将模块自身 `Activity` 注入自身。
**解决方案**
由于模块自身也可以被自身 Hook但你并不可以在模块自身注入自己 (不能递归自身的资源),若你一定要获取模块自身的资源,请直接使用即可,无需任何其它操作。
## 阻断异常 ## 阻断异常
> 这些异常会直接导致 APP 停止运行(FC),同时会在控制台打印 `E` 级别的日志,还会造成 Hook 进程“死掉”。 > 这些异常会直接导致 APP 停止运行(FC),同时会在控制台打印 `E` 级别的日志,还会造成 Hook 进程“死掉”。