sable / android-platforms Goto Github PK

It looks like the sha256 of the android 26 version changed from
cdc1846376a14b0370cc63454a129606b4a52cc50ada75ef0d4cf956b1ad2daa
to
41f4675469a852ae96442eb5d49b43dc52602c77d15d0807105638606a999484

Why?

Since things become deprecated from one version to another on android, having just the latest version of the android-platform linked to my Soot instance, shouldn't be enought to run properly?

I'm not sure if I really need all versions as dependency. Could somebody answer me this one?

Actually using Soot to instrument Android Apps.

Please upload Android 13 (API level 33) jar file. I need this for developing app with mit app inventor 2.

Hello,

I was glancing over issue number 4 and was trying to generate the android.jar and android-api-28.jar because I am required to run an analysis on an updated API level android application.
I was a bit confused by what steps are required to generate these jar files.
StevenArzt noted that the full JAR files could be created by loading the system code from a phone or emulator, converting it back to Java bytecode, and packaging it as a JAR.

I am relatively new to generating these jar files.
I do have some experience with Android programming applications and have already successfully analyzed some APK files.

For background information, the operating system I am running is Ubuntu with the latest Android Studio platform.

Any help would be much appreciated.
Thanks.

Hi, if I want to instrument app on google play apps that use android api version more than 17.How should I do?(although it will use min api version automatically,but I want to try the target api version)
I have tried to copy the eclipse android api(ex/Applications/adt-bundle-mac-x86_64-20140702/sdk/android-18,19,20 )to android-platforms folder but it doesn't work.Very appreciate watching my question,thanks!

Hello! Are the android.jar archives stubs of the Android APIs? According to Issue #4 that should not be the case but I disassemble classes at random and always see method bodies with the equivalent of throw new RuntimeException("Stub!").

For example, for android-25:

$ mkdir 25 && cd 25 && jar xf ../android-25/android.jar
$ javap -p -v -c android/system/Os.class
...
  public static int write(java.io.FileDescriptor, byte[], int, int) throws android.system.ErrnoException, java.io.InterruptedIOException;
    descriptor: (Ljava/io/FileDescriptor;[BII)I
    flags: ACC_PUBLIC, ACC_STATIC
    Code:
      stack=3, locals=4, args_size=4
         0: new           #2                  // class java/lang/RuntimeException
         3: dup
         4: ldc           #3                  // String Stub!
         6: invokespecial #4                  // Method java/lang/RuntimeException."<init>":(Ljava/lang/String;)V
         9: athrow
...

Please give andoird version 12 jar file

Hi,

Google has released many Android platform versions since the last update of this project. I have been told that the JAR files in this project are "stubbed". How can I make "stubbed" versions of JAR files for new Android platforms and contribute to this project? I would like to help.

Thanks.

I want the android-platforms versions from 17 to 23 to analyse android applications and avoid the below warning given in soot.
warning: Android API version '21' not available, using minApkVersion '9' instead
I would be relay grateful, if this repository is updated with the mentioned versions.