feat(icons): add icon support for .aab files

[infoanilsahu]

Description

Fixes #3327

Contribution Guidelines

• By creating this pull request, I acknowledge that I have read the Contribution Guidelines for this project
• I have read the Code Of Conduct and promise to abide by these rules

[github-actions]

Preview

Thank you for creating a pull request. This preview shows you how your icon will look on the different themes:

Check how your icon fits in a 16x16 grid with our Pixel Perfect Checker by following this link.

You can find more information on how to contribute in the contribution guidelines.

[infoanilsahu]

is any changes required

[PKief]

@infoanilsahu Thanks for creating a PR. I was wondering, why can't we reuse the already existing android icon for this?

[infoanilsahu]

Hi @PKief,

Thanks for the feedback

The existing Android icon is currently associated with .apk files. However, .apk (Android Package Kit) and .aab (Android App Bundle) are fundamentally different artifacts in the Android build and distribution pipeline.

APK is the final, installable package that runs directly on Android devices.

AAB is a publishing format introduced by Google Play that contains split configurations and is processed by Play Store to generate optimized APKs per device.

Although both are Android-related, they serve different purposes and represent different stages of distribution. From a UX perspective, using the same icon for both file types can create ambiguity, especially in projects where both artifacts coexist (which is common in modern Android CI/CD workflows).

Providing a distinct icon for .aab:

Improves visual clarity

Preserves semantic distinction between build artifacts

Helps developers quickly identify the correct file at a glance

That said, if the project prefers reusing the existing Android icon for consistency, I’m happy to adjust accordingly. Just let me know your preference.