-
Notifications
You must be signed in to change notification settings - Fork 547
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
Missing proguard rule for transfer util #806
Comments
Also is there any reason for which consumerProguardFiles are not provided with the library and developers needs to add them manually? |
Hi @freszu , The S3 module is distributed as a JAR and not an AAR. We are considering transitioning, but evaluating if this would break any of our customers. |
Hi @freszu, I wasn't able to reproduce the exact bug, but I think I have a potential fix for your issue. Would it be possible to test your app with this code base to see if your issue is resolved? If not, would you be able to provide us with more information regarding what proguard rules you used to obfuscate your code? For example, did you use any third-party library for obfuscation? Thank you. |
Hi @raphkim sorry for coming with an answer so late. So i managed to make a local build with your changes and use generated jars instead.
About our setup we are not using anything extraordinary and recently made switch from proguard to r8 but the problem still occurs. We applied all the rules mentioned in the https://github.com/aws-amplify/aws-sdk-android/blob/master/Proguard.md + the one mentioned in first post to overcome the issue with missing enum. Release build is configured with Other people ran into the same problem in the past but issue was closed: #704 |
See the following related issues: - #704 - #806 - #2141 - aws-amplify/amplify-android#939
See the following related issues: - #704 - #806 - #2141 - aws-amplify/amplify-android#939
See the following related issues: - aws-amplify#704 - aws-amplify#806 - aws-amplify#2141 - aws-amplify/amplify-android#939
See the following related issues: - #704 - #806 - #2141 - aws-amplify/amplify-android#939
Describe the bug
Recently we migrated from aws '2.6.30' to '2.12.2' since then the upload is failing on obfuscated version of our app(checked with 2.12.5 as well and problem still exists).
We resolved that by adding
to our proguard setup.
To Reproduce
Create obfuscated version of the app and try to upload anything using transfer utility
Which AWS service(s) are affected?
Expected behavior
Upload should be successful
Environment Information (please complete the following information):
Additional context
Original stack trace:
The text was updated successfully, but these errors were encountered: