In the tasks list json the status field has different formats #2464
Comments
|
👋 @dri-mobisec |
4 tasks
ajinabraham
added a commit
that referenced
this issue
Nov 29, 2024
…es (#2470) * Dockerfile QA * Add sdk-build-tools to Docker image * Replace biplist with plistlib std lib * Fixed a bug in iOS pbxproj parsing * Added support for APK parsing with aapt2/aapt * Use aapt/aapt2 as a fallback for APK parsing, files listing and string extraction * Added "started at" to Scan task queue model #2463 * Tasks List API to return string status #2464 * Replaced all minidom calls with defusedxml.minidom * Code QA on android manifest data extraction and parsing * Improved android file analysis * Improved android manifest data extraction * Improved android icon file extraction * Improved android app name extraction * Improved android appstore package details extraction * Android string extraction to fallback on aapt2 strings * APK analysis arguments refactor * Handle packed APKs, refactor unzip to handle malformed APK files * Handle reserved filename conflict during ZIP extraction * Explicit Zipslip handling during ZIP extraction * Graceful files extraction on unzip failure * Removed bail out and continue analysis * Moved androguard parsing to the start of static analysis * AndroidManifest.xml fallback from apktool to androguard during extraction and parsing * Updated Tasks UI to show started at
|
This is addressed in 4.2.8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ENVIRONMENT
EXPLANATION OF THE ISSUE
when calling the api/v1/tasks endpoint, in the tasks lists the "status" field is either a string or an object depending on the status itself.
This is a problem because the json format is coherent and it makes impossible to create a proper mapper for the object;
The text was updated successfully, but these errors were encountered: