[
https://issues.apache.org/jira/browse/TIKA-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916700#comment-17916700
]
ASF GitHub Bot commented on TIKA-4365:
--------------------------------------
subbudvk commented on PR #2085:
URL: https://github.com/apache/tika/pull/2085#issuecomment-2612380253
@tballison you are right. The Jar detector decides content based on the
presence of MANIFEST.MF. The android package bundle will also have MANIFEST.MF,
so to guarantee the order and JarDetector doesn't return jar based on
MANIFEST.MF and since other android types are already handled in JarDetector,
I changed here.
Let me know if you have comments.
> Support Android Bundle aab detection
> ------------------------------------
>
> Key: TIKA-4365
> URL: https://issues.apache.org/jira/browse/TIKA-4365
> Project: Tika
> Issue Type: Bug
> Components: tika-core
> Reporter: Subbu
> Priority: Critical
>
> AAB file goes through DefaultZipContainerDetector and gets detected as
> _application/java-archive_ since it has MANIFEST.MF via JarDetector.
> They have their own content type as mentioned in tika-mimetypes.xml -
> application/x-authorware-bin
> [https://github.com/apache/tika/blob/6a12d7cf1a2ee37dce899933a05520604330c947/tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml#L3485]
> The AAB file structure has a AndroidManifest.xml similar to apk archive but
> in [base/manifest/|http://base/manifest/] directory.
> Android Dev documentation reference :
> [https://developer.android.com/guide/app-bundle/app-bundle-format]
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
