Auto rename defaut 1.apk to match your version eg. framework_2.11.1.apk

[Sappurit]

Currently, we have a problem where users are not aware that the framework stored at %HOMEPATH%\AppData\Local\apktool\framework\1.apk is actually a copy of the internal file at brut.apktool/apktool-lib/src/main/resources/brut/androlib/android-framework.jar.

This file is the android.jar resources.arsc file from every new API release. The problem is that users never update this file and thus encounter many errors.

I have to ask ChatGPT to fix this problem.

1. Automatic extract 1.apk and rename to framework_2.11.1.apk
2. Automatic select framework_2.11.1.apk when using apktool_2.11.1.jar

[iBotPeaches]

Generally I believe I would move to a setup that Apktool recognizes the format of the resource file and tracks all of them internally and copies out the one it needs under the api-{version}-{patch}.apk name

Since I don't want to attach an internal framework file to an apktool version. They are more connected to AOSP releases.

[HassanMirza01]

Currently, we have a problem where users are not aware that the framework stored at %HOMEPATH%\AppData\Local\apktool\framework\1.apk is actually a copy of the internal file at brut.apktool/apktool-lib/src/main/resources/brut/androlib/android-framework.jar.

This file is the android.jar resources.arsc file from every new API release. The problem is that users never update this file and thus encounter many errors.

I have to ask ChatGPT to fix this problem.

1. Automatic extract 1.apk and rename to framework_2.11.1.apk
2. Automatic select framework_2.11.1.apk when using apktool_2.11.1.jar

i think this issue linked to attrs.xml values too which gets missing and layout/xml folder xmls get weird attributes which later apktool dont recognize for rebuild? Its fine in on Android 15 as attrs gets extracted well in this sdk, but in A14 where it was started, i still see missing attrs and have to add missing ones in attrs.xml and rename their reference type in layouts and xml folder.