Open MichalSmaliraITM opened 3 months ago
I am from the R8 team, and this looks like a missing dependency. The classes mentioned are references in the input, but not present. If these classes are in an optional dependency, then adding the rules generated in X/android/app/build/outputs/mapping/release/missing_rules.txt
to your proguardFiles
(see https://developer.android.com/build/shrink-code#enable) should work.
Thanks @sgjesse I've made it as a workaround right away I do however expect stripe team to look into it to either fix or adjust troubleshooting section to include info about that!
can you guys show the changes made to make it work? I'm stuck here
@Orteu adding
-dontwarn com.stripe.**
will silence R8 warnings that became errors in AGP 8+
While adding -dontwarn
is a workaround, the stripe team should ensure that these are not present when depending on the library. Either by adding explicit -dontwarn
's to the consumer keep runes (if this is by design optional dependencies) or add the required transitive dependencies to the POM.
Im using react native expo and anyone can help me on how can i resolve this?? @sgjesse where i need to add -dontwarn in my react native expo application can you share that info please?
I am not familiar with the Expo project setup, and cannot give any info on where Proguard configuration rules are located.
@udayaprakashjayaraman Were you able to fix this?
@udayaprakashjayaraman Were you able to fix this?
@divyanshu-bantr with a workaround, I created new project and replaced my existing code on that and installed required packages and it started working for me.
Quick fix - I removed these valuesenableProguardInReleaseBuilds: true
and enableShrinkResourcesInReleaseBuilds: true,
from the expo-build-properties
plugin in app.config
This isn't perfect since minifying step does not occur and the final build is larger in size. Also, this is avoiding the errors rather than fixing them
Where you able to fix this? having the same issue with expo managed project
@bkjp-dev I have disabled Proguard in release builds for now. Not ideal and the google play console also gives a warning when you upload the aab
. It is what it is for now..
Describe the bug Production build of android fails with error:
To Reproduce Steps to reproduce the behavior:
Expected behavior App is built without error
Additional context Integration works properly on both android and iOS emulators in debug mode, no errors or warnings. iOS Prod build works fine as well.