ttnisal

Hi @vladd-g I have pasted the whole code from that file to my proguard-rules.pro file. But it still has this issue. This is the full error. ``` {"adaptyCode":2006,"localized Description":"Failed to...

Hi @vladd-g , Here are the verbose logs ``` [21:43:48] D | ReactNativeJS ▶︎ '[2024-01-06T04:43:48.131Z] [[email protected]] "setLogLevel": Calling method', {} [21:43:48] D | ReactNativeJS ▶︎ '[2024-01-06T04:43:48.267Z] [[email protected]] "parse": Decoding string...',...

Hi @vladd-g , yes I have like this ``` signingConfig signingConfigs.release minifyEnabled enableProguardInReleaseBuilds proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro" ```

Hi @vladd-g , I didn't quite get what you meant as same level. All the proguard rules mentioned [here](https://github.com/google/gson/blob/main/gson/src/main/resources/META-INF/proguard/gson.pro) was place inside the `proguard-rules.pro` file in the `android/app` folder. And...

Hi @vladd-g, yes they are on the same level in the project hierarchy. Are there any other library that can cause the obfuscation?

Hi @vladd-g , by any chance does the package `@adapty/react-native-ui` need any proguard rules?

Hi @vladd-g, I have analysed the APK in release mode. I think as the following image the adapty and gson classes are not obfuscated. However the other source code seems...

@vladd-g, This is the expanded view for the package. But I can see something like this

HI @vladd-g, seems like it's not

Hi @vladd-g , No luck in adding that also. To make sure the proguard-rules.pro file is working fine. I have added the following config to exclude all classes from being...