Skip to content

Missing consumer ProGuard rules causes AWSS3V4Signer removal with AGP 9 (R8 full mode) #3686

Description

@P-Emmy

Describe the bug
R8 full mode (enabled by default in AGP 9) strips com.amazonaws.services.s3.internal.AWSS3V4Signer

To Reproduce

  1. Create a simple app that initializes an S3 client (default signer).
  2. Build a release APK/AAB with minifyEnabled=true (no custom keep rules).
  3. Run the app: it crashes on the first S3 call with
    java.lang.IllegalStateException: Cannot create an instance of com.amazonaws.services.s3.internal.AWSS3V4Signer

Which AWS service(s) are affected?
com.amazonaws:aws-android-sdk-s3

Expected behavior
AWS SDK should ship consumer ProGuard rules so required signer classes are kept when R8 full mode is on.

Environment Information (please complete the following information):

  • AWS Android SDK Version: 2.81.1
  • Specific to simulators: No

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workings3Issues with the AWS Android SDK for Simple Storage Service (S3).

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions