Skip to content

Conversation

@fasiho7
Copy link

@fasiho7 fasiho7 commented Jan 29, 2026

This PR closes #issue_number

Description

Briefly describe what changed and why. Reference the related issue where applicable.


AI Tool Disclosure

Check exactly one option.

  • This contribution does not include AI-generated content.
  • This contribution includes AI-generated content.

If AI tools were used to generate or substantially modify code or text, complete the following.

  • AI tools used: e.g. ChatGPT, GitHub Copilot, Claude.
  • Models and versions: e.g. GPT-, Claude .
  • Prompt summary: brief description of the key prompts or instructions.
  • Your mobile security expertise level: low, medium, high.

For first-time contributors using AI tools.

  • Provide an export of the AI chat or session, for example a shared link or PDF attachment.
  • Ensure the commit history shows an initial commit with AI-generated content followed by commits that demonstrate review, correction, and improvement.

Undisclosed use of AI tools will result in the PR being closed. Large rewrites or bulk changes generated by AI require explicit prior approval from the maintainers. Learn more in "Use of AI tools in contributions".


Contributor Checklist

  • I have read and understood the contributing guidelines.
  • I followed the project style guide.
  • I validated the technical correctness of my changes and understand the topic.
  • This PR adds clear value and is not spam or low-effort content.

Relevant documentation.

Contributors are expected to understand basic git and GitHub workflows, including forks, branches, commits, and pull requests. The project does not provide training. Pull requests that do not meet these minimum requirements may be closed without review.

- Update MASTG-APP-0026.md with comprehensive known issues section
- Add specific testing guidance to MASTG-TEST-0089.md
- Document workaround guidelines for 32-bit vs 64-bit analysis
- Include reference to main repository issue commjoen/uncrackable_app#10
- Provide troubleshooting steps for users affected by the bug

Fixes documentation gap for iOS CrackMe Level 2 anti-debugging validation issue
- Aligns with mastg-test.instructions.md requirement
- Enforced by new lint rule in .markdownlint.jsonc
- Changed @MASTG-TOOL-0038 and @MASTG-TOOL-0106 to @MASTG-TECH-0044
- Changed @MASTG-TOOL-0129 to @MASTG-TECH-0078
- Changed @MASTG-TOOL-0036 to @MASTG-TECH-0096
- Aligns with mastg-test.instructions.md requirement
…iles

iOS Files Fixed:
- MASTG-TEST-0091: Replaced @MASTG-TOOL-0031, @MASTG-TOOL-0139, @MASTG-TOOL-0066 with @MASTG-TECH-0079
- MASTG-TEST-0081: Replaced @MASTG-TOOL-0114 with @MASTG-TECH-0075

Android Files Fixed:
- MASTG-TEST-0011: Replaced @MASTG-TOOL-0038, @MASTG-TOOL-0106 with @MASTG-TECH-0044
- MASTG-TEST-0011: Replaced @MASTG-TOOL-0129 with @MASTG-TECH-0078
- MASTG-TEST-0011: Replaced @MASTG-TOOL-0036 with @MASTG-TECH-0096

Total fixed: 6 more references (11 total so far)
Aligns with mastg-test.instructions.md requirement
…iles

iOS Files Fixed:
- MASTG-TEST-0052: Replaced 2x @MASTG-TOOL-0038 with @MASTG-TECH-0053
- MASTG-TEST-0068: Replaced @MASTG-TOOL-0038 with @MASTG-TECH-0064
- MASTG-TEST-0075: Replaced @MASTG-TOOL-0129 with @MASTG-TECH-0078

Total fixed: 4 more references (15 total so far)
Aligns with mastg-test.instructions.md requirement
- MASTG-TEST-0076: Fixed 3x @MASTG-TOOL-0129 → @MASTG-TECH-0078
- Total fixed: 3 more references (18 total so far)
- Aligns with mastg-test.instructions.md requirement
…rm test files

iOS Files Fixed:
- MASTG-TEST-0077: Replaced 2x @MASTG-TOOL-0129 with @MASTG-TECH-0078
- MASTG-TEST-0071: Replaced @MASTG-TOOL-0129 with @MASTG-TECH-0078
- MASTG-TEST-0071: Replaced @MASTG-TOOL-0038 with @MASTG-TECH-0053

Total fixed: 3 more references (21 total so far)
Aligns with mastg-test.instructions.md requirement
Android File Fixed:
- MASTG-TEST-0028: Replaced 2x @MASTG-TOOL-0004 with @MASTG-TECH-0001
- MASTG-TEST-0028: Replaced @MASTG-TOOL-0018 with @MASTG-TECH-0014
- MASTG-TEST-0028: Replaced @MASTG-TOOL-0031 with @MASTG-TECH-0079

Total fixed: 5 more references (26 total so far)
Aligns with mastg-test.instructions.md requirement
Android File Fixed:
- MASTG-TEST-0029: Replaced @MASTG-TOOL-0035 with @MASTG-TECH-0014
- MASTG-TEST-0029: Replaced 4x @MASTG-TOOL-0018 with @MASTG-TECH-0014

Total fixed: 5 more references (31 total so far)
Aligns with mastg-test.instructions.md requirement
…nce test files

Android Files Fixed:
- MASTG-TEST-0045: Replaced @MASTG-TOOL-0142 with @MASTG-TECH-0086
- MASTG-TEST-0048: Replaced @MASTG-TOOL-0031, @MASTG-TOOL-0027 with @MASTG-TECH-0079
- MASTG-TEST-0051: Replaced 2x @MASTG-TOOL-0009 with @MASTG-TECH-0087

Total fixed: 4 more references (35 total so far)
Aligns with mastg-test.instructions.md requirement
Android File Fixed:
- MASTG-TEST-0039: Replaced @MASTG-TOOL-0018 with @MASTG-TECH-0014

Total fixed: 1 more reference (36 total so far)
Aligns with mastg-test.instructions.md requirement
… attacks testing

- Added comprehensive documentation for Android 16's new accessibilityDataSensitive flag
- Included implementation examples for View-based and Jetpack Compose apps
- Added testing recommendations for the new protection mechanism
- Updated MASTG-TEST-0035 with latest Android security best practices
- Addresses partial occlusion scenarios with system-level protection

References:
- https://android-developers.googleblog.com/2025/12/enhancing-android-security-stop-malware.html
- https://developer.android.com/privacy-and-security/risks/tapjacking#mitigations
@github-actions
Copy link

Thank you for your contribution! However, this PR does not reference any issues.

To contribute to this project, please:

  1. Find an existing issue you'd like to work on, or create a new one
  2. Get assigned to the issue
  3. Reference the issue in your PR using keywords like "Fixes 0x4 - About Burp Suite #123" or "Closes 0x4 - About Burp Suite #123"

Please reopen this PR once you have linked it to an issue you are assigned to.

@github-actions
Copy link

Automated moderation result.

Verdict, ai-gen-needs-review.
Confidence, 85.

Reasons.
No AI disclosure provided in the PR
PR contains substantial changes
Generic description in the body
High number of files modified

Evidence.

  • "Briefly describe what changed and why.", Generic PR body lacking detail
  • No checked box for AI disclosure
  • 20 files changed indicates potential bulk edits

Suggested action, Request further justification for the changes and review evidence of AI use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants