A8. Determine whether the reflection workarounds are still required
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 66
Description
Two shipped projects read private fields out of obfuscated AARs: CxrApi.I for the serial number, and a ServiceConnection field scan on CXRLink. Establish whether current SDK versions still require this. If yes, pin the AAR version and add a hardware smoke test, because no unit test can detect the breakage.
Section A — Hardware verification (needs a Rokid device). Registered from ISSUES.md.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Section A entry in ISSUES.md and inspect the two shipped projects that use CxrApi.I and the ServiceConnection field scan. Compare those reflection workarounds with the current SDK AARs, then verify on a Rokid device if needed. Done means establishing whether they remain necessary; if they do, pinning the AAR version and adding the hardware smoke test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100