Skip to content

Removing resolve absolute path of XML files - #109

Closed
xotohop wants to merge 1 commit into
MobSF:mainfrom
xotohop:main
Closed

Removing resolve absolute path of XML files#109
xotohop wants to merge 1 commit into
MobSF:mainfrom
xotohop:main

Conversation

@xotohop

@xotohop xotohop commented Jun 23, 2025

Copy link
Copy Markdown

Hi @ajinabraham!

When scanning XML files (manifests, etc), absolute paths are reported, not relative paths from the tool's start location

As a result, without additional normalization on the report receiver side (Vulnerability Managers, ASOC, etc) duplicates start to accumulate under certain circumstances

ajinabraham added a commit that referenced this pull request Aug 10, 2026
Stop forcing absolute paths in Android XML and iOS Info.plist results
so they match Semgrep/source reporting and reduce ASOC duplicates (#109).

Co-authored-by: Cursor <cursoragent@cursor.com>
@ajinabraham

Copy link
Copy Markdown
Member

Thanks @xotohop — this is fixed on #121 with a shared report_path() helper that:

  1. Drops forced .resolve() absolute paths for Android XML (your change)
  2. Applies the same for iOS Info.plist ATS findings
  3. Prefers cwd-relative paths when the file is under the working directory (better ASOC/VM dedup even if the scan root was absolute)

Closing in favor of #121 once that merges.

@ajinabraham

Copy link
Copy Markdown
Member

Addressed in #121

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants