v1.2.2 released!!
v1.2.2 发布啦！！

Changelog
- Magisk zip now contains a manager
- Properly handle hidden apps
- Optimize core size
- Make hook functions' names more reasonable for debugging
- Fix DoH
- Swipe to refresh the app list
- Fix hooks on non-ASCII named methods
- Optimize logging on the release build
- Fix pending hook on Android S
- Deprecate SandHook (2/4): You cannot switch to SandHook in regular ways

更新日志
- Magisk 模块 zip 现在自带一个管理器了
- 正确处理隐藏应用
- 优化 core 大小
- 使 hook 函数的名字在 debug 时候更加合理
- 修复 DoH
- 添加下拉刷新应用列表
- 修复非 ASCII 名字的函数的 hook
- 优化日志
- 修复 Android S 上的延迟 hook
- 弃用 SandHook (2/4)：已经无法以通常方法切换到 SandHook

*Notes: manager will automatically upgrade after the first reboot. Please wait patiently until the new manager is installed.
*注意：管理器会在第一次重启后自动更新，请耐心等待。

Undoubtedly, LSPosed works perfectly on Android S DP2!

不出所料，LSPosed 在 Android S DP2 上完美运行！

Many people report app crashing recently. It's NOT LSPosed/Riru's bug. It's from Google‘s recent update of WebView (89.0.4389.90). Please wait for Google's fix.

很多人说最近应用开始崩溃。这不是 LSPosed 或 Riru 的问题，是谷歌最近的 WebView 的更新（89.0.4389.90）引起的。请等待谷歌的修复。

Edit: 89.0.4389.105 fixed
编辑：89.0.4389.105 修复了

Many users report that after upgrading to latest Magisk Canary, LSPosed shows yellow warning. This issue is caused by Magisk and we have already reported to Magisk devs. Temporary workaround is to re-flash LSPosed and reboot. If it does not help, rollback to previous Magisk, re-flash LSPosed again and reboot.

很多用户表示升级到最新的 Magisk Canary 之后 LSPosed 提示黄色警告。这个问题是由 Magisk 引起的，并且我们已经反馈给 Magisk 开发者。临时解决方案是重刷 LSPosed 并重启。若未能解决问题，可尝试退回上一个版本的 Magisk Canary 并且再次重刷 LSPosed，然后重启。

https://play.google.com/store/apps/details?id=org.lsposed.manager

LSPosed published on Google Play.
LSPosed 已在Google Play发布。

We are discussing an API for communication between modules and Xposed Framework. (can be used to set scope, read scope, or so...)

Suggestions from modules' developers are warmly welcomed.

1.3.5 Released!
1.3.5 发布啦！

Changelog
- Reduce size by using self-build libcxx
- Fix crash when a repo does not have any release
- Support hooking default methods of interfaces (a feature of Java 8)
- Replace DobbySymbolResolver with AndroidELF
- Fix in some rare case, LSPosed cannot be activated
- Higher optimization level of compiling
- Refine installation scripts
- Minimum Magisk requirement updated to 21+ (even so, 22.1+ is strongly recommended)
更新日志
- 通过自编译 libcxx 优化大小
- 修复当仓库有模块没有发行版本时候管理器会崩溃
- 支持 hook 接口的默认方法（这是个 Java 8 的新特性）
- 使用 AndroidELF 代替 DobbySymbolResolver
- 修复一个罕见的 LSPosed 不能激活的问题
- 更高的编译优化等级
- 优化安装脚本
- 要求 Magisk 版本至少为 21+（请尽量使用 22.1 或以上版本）

*Notes: Now that LSPosed is mature and stable enough, we are working on an API for communication between module and framework, and a simple non-root framework. So the update frequency will be reduced.
*注意：目前 LSPosed 已经足够成熟稳定，我们开始转向开发模块与框架的通讯接口，以及一个简单的非 root 框架。因此更新频率会有所下降。

A rare but severe bug found on Magisk by LSPosed developers. Effected versions cover from 21.0 to latest 22.1. In short, this bug might cause your device bootloop after installing any module with small probability. We noticed there's a bug affecting modules' loading for a long time but not until today we finally located it.

LSPosed 开发团队发现 Magisk 的一个罕见但是严重的 bug。该 bug 影响范围从 21.0 一直到 22.1。简单来说，这个 bug 小概率会使你在安装任意模块后导致设备无限重启。我们很早之前就发现有个 bug 影响模块加载，但是直到今天我们才真正定位到它。



*fixed in the latest canary
*最新 canary 已修复

For Chinese users ONLY:

我们开发组收到消息，某助手被破解并且使用了自建服务器提供模块下载。我们觉得有必要提醒各位用户，切勿从非官方渠道下载安装 Magisk、Riru 和 LSPosed，以免被植入恶意程序。

Magisk 23 is released! We strongly recommend users to update since it fixes the sepolicy bug.

Magisk 23 发布了。因其修复了 sepolicy 的 bug，我们强烈推荐用户升级。

1.4.0 released!
1.4.0 发布辣！

Changelog
- Fix in a rare case system modules not working
- Workaround for that some low-quality modules stick post-fs-data.sh
- Update native hook API
- Follow some changes on Android S (support S Beta 1 now)
- Restrict hidden API bypass to modules' classloader only
- Add an option to help modules to hide their icons on Android Q+
- New way to better support dual apps/multi-users*
更新日志
- 修复极小概率的系统模块无法生效
- 解决某些低质模块卡死 post-fs-data.sh 的情况
- 更新 native hook 的 API
- 跟进一些 Android S 上的修改（兼容 Android S Beta 1）
- 限制仅模块类加载器允许绕过隐藏 API
- 添加选项帮助模块在 Android Q+ 上隐藏图标
- 支持双开、多开应用的新策略*

* Previously LSPosed only recognize modules from the primary user. However, this strategy is not good and leads to some problems: some modules require getting installed app lists for configuration but they cannot do so across users; some require reading themselves from the hooked apps but they cannot do so from non-primary users; some users want to configure modules differently on different users which is not feasible previously. Thus LSPosed now requires every module to be installed to the user on which the apps they want to hook are installed. Some devices restrict modules from installing onto some users. In such a case, you can install them from the manager (but it's not recommended). Notice that the module won't take extra space if you install it on different users: there will only be one apk.
* 之前 LSPosed 仅识别安装在主用户的模块，该策略并非完美且导致诸多问题：一些模块需要获取安装应用列表以进行配置，但是该列表无法跨用户获取；一些模块需要从被注入应用获取本身，这样会在非主用户无法正常工作；一些用户希望分用户对模块进行配置，这也无法实现。于是，LSPosed 现在要求模块必须安装到对应用户上以注入到该用户上的应用。某些设备不允许模块安装到某些用户上，此时可以利用管理器安装（非万不得已时不推荐）。注意，安装在其他用户的模块不会占用额外空间：永远只有一个 apk。

Please join discussion group before commenting. Otherwise, you will be temporally muted by bot automatically. We request this because so many people ask questions in channel comment and they cannot see the replies from the discussion group.
请在评论前加入讨论组，不然会被 bot 自动临时禁言。如此要求是由于许多在评论提问的人会看不到来自讨论组的回复。

1.4.1 released!
1.4.1 发布辣！

Changelog
- Fix in MIUI dual modules added by manager will be deleted by reboot
- Automatically switch user when launching apps or modules of secondary users.
- Support launching modules with android:showForAllUsers="true" without switching user
- Fix Riru installation check
- Fix activation of modules from non-primary users

更新日志
- 修复 MIUI 下管理器添加的双开模块重启被自动移除
- 启动次用户模块或者应用时自动切换用户
- 支持不切换用户下启动带 android:showForAllUsers="true" 的模块
- 修复检查 Riru 安装
- 修复非主用户下模块的激活