HighCapable / HighCapable/YukiHookAPI

Any plans to support libxposed API 101 to maintain compatibility for YukiHookAPI -built modules?

Open
#121 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
2.2k
Forks
157
Avg merge
9h 27m
Merged PRs (30d)
2

Description

Would you consider upgrading the libxposed to API 101, or implementing forward compatibility up to this API? This is critical for maintaining the compatibility of Xposed modules built with YukiHookAPI with future releases of the Xposed API.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the libxposed dependency and the API compatibility entry points in the Kotlin project, then review how YukiHookAPI-built modules interact with the supported Xposed API. Done means an agreed implementation supports libxposed API 101 or clearly provides forward compatibility without breaking existing modules.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.