search

Android1500 / GpsSetter

Xposed module which will set location where you want without effect mock location.
321 stars 44 forks source link

Bump com.highcapable.yukihookapi:api from 1.1.6 to 1.1.9 #54

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps com.highcapable.yukihookapi:api from 1.1.6 to 1.1.9.

Release notes

Sourced from com.highcapable.yukihookapi:api's releases.

1.1.9

YukiHookAPI 1.1.9 Released

  • Change the type of dependent library from Java Library (jar) to Android Library (aar)
  • Remove the inspection function of internal methods and parameters through Hook or reflection API
  • Fixed the problem that YukiHookDataChannel automatically segmented data sending function could not work normally (exception would still be thrown)
  • Added the ability to manually modify the maximum data byte size allowed by YukiHookDataChannel to be sent at one time according to the limitations of the target device
  • Remove the restriction that YukiHookDataChannel can only be used in module Activity, now you can use it anywhere
  • Modify and standardize the broadcast Action name used by YukiHookDataChannel
  • Fix the problem that BadParcelableException occurs when YukiHookDataChannel has different modules with the same host
  • Added ExecutorType, you can get the type of known Hook Framework through YukiHookAPI.Status.Executor.type
  • YukiHookModulePrefs renamed to YukiHookPrefsBridge
  • Modify YukiHookPrefsBridge to be implemented as a non-singleton, as a singleton may cause data confusion
  • Deprecated Context.modulePrefs(...) method, please move to Context.prefs(...)
  • YukiHookPrefsBridge adds native method, which supports storing private data in modules and hosts directly as native storage
  • Integrate the storage method in YukiHookPrefsBridge to YukiHookPrefsBridge.Editor, please use edit method to store data
  • YukiHookPrefsBridge adds contains method
  • Cache dynamically created proxy objects in YukiHookPrefsBridge, try to fix problems that may cause OOM in the host and modules
  • Modify the proxy class of the Activity proxy function to be dynamically generated to prevent conflicts caused by injecting different modules into the host
  • Fixed some other possible problems

For more details, please check the changelog.

YukiHookAPI 1.1.9 已发布

  • 将依赖库的类型由 Java Library (jar) 修改为 Android Library (aar)
  • 移除通过 Hook 或反射 API 内部方法、参数的检查功能
  • 修复 YukiHookDataChannel 自动分段发送数据功能不能正常生效 (依然会抛出异常) 的问题
  • 新增可以手动根据目标设备的限制修改 YukiHookDataChannel 允许一次发送的最大数据字节大小
  • 移除 YukiHookDataChannel 只能在模块 Activity 中使用的限制，现在你可以在任何地方使用它
  • 修改并规范 YukiHookDataChannel 使用的广播 Action 名称
  • 修复 YukiHookDataChannel 在不同模块同一宿主的情况下出现 BadParcelableException 异常的问题
  • 新增 ExecutorType，可以通过 YukiHookAPI.Status.Executor.type 来获取已知 Hook Framework 的类型
  • YukiHookModulePrefs 更名为 YukiHookPrefsBridge
  • 修改 YukiHookPrefsBridge 为非单例实现，作为单例可能发生数据混淆的问题
  • 作废了 Context.modulePrefs(...) 方法，请转移到 Context.prefs(...)
  • YukiHookPrefsBridge 新增 native 方法，支持直接作为原生存储在模块和宿主中存储私有数据
  • 整合 YukiHookPrefsBridge 中的存储方法到 YukiHookPrefsBridge.Editor，请使用 edit 方法来存储数据
  • YukiHookPrefsBridge 新增 contains 方法
  • 缓存 YukiHookPrefsBridge 中动态创建的代理对象，尝试修复可能会导致宿主、模块出现 OOM 的问题
  • 修改 Activity 代理功能的代理类为动态生成，防止不同模块注入宿主后造成冲突
  • 修复一些其它可能出现的问题

详情请查看更新日志。

1.1.8

YukiHookAPI 1.1.8 Released

... (truncated)

Commits
  • 635e8b5 Automatically compile documentation (1.1.9)
  • 6b4804c Update version to 1.1.9
  • 51a9f42 Fix some contents problem in NameRules documentation
  • f9cdcc5 Modify make YukiHookPrefsBridge not singleton to fix some duplicate assignmen...
  • b41897f Modify suppress some warn lint checking in DexClassFinder, HandlerDelegateCal...
  • 9e1a6f2 Update demo
  • 7f7b8e9 Update api-exception documentation
  • 390ee9e Modify change YukiHookModulePrefs name to YukiHookPrefsBridge and make it sup...
  • e298f19 Fix prefs object created every time maybe called app OOM problem in YukiHookM...
  • b61bd33 Added XSharedPreferencesDelegate to fix no Xposed environment class not found...
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #58.