Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Application unpacking supports Android architecture #1735

Open
rakuyoMo opened this issue Nov 24, 2024 · 7 comments
Open
Labels
enhancement New feature or request

Comments

@rakuyoMo
Copy link

rakuyoMo commented Nov 24, 2024

描述 | Description

An Android app may generate multiple apk installation packages at one time: universal, 64-bit or 32-bit. Therefore, the information of product version, build version, application name, and packaging type are consistent, and they belong to the same channel, but the architecture is different. (The same app store may upload multiple architecture apks at the same time)

Now when uploading apk, the architecture information will not be displayed when the application is unpacked, and the file name will not contain the corresponding information when downloaded, which will make it impossible to distinguish when actually using it.

In addition to displaying the architecture in the unpacking information, it is hoped that the architecture information can be added to the file name when downloading the apk. This is a very critical information for distinguishing which apk to use when publishing to the app store.

Hope to add this function, thank you very much!

@rakuyoMo rakuyoMo added the enhancement New feature or request label Nov 24, 2024
@icyleaf
Copy link
Member

icyleaf commented Nov 24, 2024

Android cannot parse architectures or I have not been able to find where to obtain them; what is known so far is that they can be obtained at runtime layer.

@rakuyoMo
Copy link
Author

rakuyoMo commented Nov 24, 2024

So I hope you can reconsider this request: #1611, which can be used as a compromise solution at this stage.

CI can build names like "[channel_name]-arm64-v8a_2024_11_07_18_24_1.22.1.apk", "[channel_name]-universal_2024_11_07_10_32_1.22.0.apk", so that users can clearly know what architecture they are downloading.

Otherwise, at this stage, unless the architecture is used as a channel, it is difficult to distinguish the architecture of different apk files in one channel. And it feels inappropriate to use the architecture as a channel.

@rakuyoMo
Copy link
Author

Or consider using apt dump badging app.apk | grep 'native-code' ?

@icyleaf
Copy link
Member

icyleaf commented Nov 24, 2024

aapt is closed source project. i need find other way to do it with pure code.

@rakuyoMo
Copy link
Author

OK.

I just wanted to let you know that it is very, very important to allow users to distinguish the architecture of the apk directly from the filename of the downloaded file.

Looking forward to your implementation of this feature. Have a nice day.

@icyleaf
Copy link
Member

icyleaf commented Nov 24, 2024

And aapt only return native-code with native code, else it will return empty.

@TOT-JIN
Copy link

TOT-JIN commented Nov 26, 2024

I need this feature too !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants