-
Notifications
You must be signed in to change notification settings - Fork 15
Functionalities not working in release mode #102
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
Comments
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.
|
@ttnisal could you please also add some Adapty verbose logs around the error? but anyway, it totally looks like an obfuscation problem, not the SDK bug |
Hi @vladd-g , Here are the verbose logs
|
Hi @ttnisal, do you have something like |
Hi @vladd-g , yes I have like this
|
@ttnisal are those proguard rules above in the right |
Hi @vladd-g , I didn't quite get what you meant as same level. All the proguard rules mentioned here was place inside the And in the
Could you explain a little bit more? |
@ttnisal by "same level" I meant same level in the project hierarchy, that would mean that you've chosen the right
|
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 |
Hi @ttnisal
I think no, it looks like only these two.
Again, it doesn’t look so, as the json from your snippet is from a model that shares the same package Can you perform Build -> Analyze APK in Android Studio to inspect what exactly got obfuscated? |
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 to be obfuscated. ![]() Do you have any thoughts on this? |
@ttnisal could you please expand com/adapty/internal/crossplatform/ui? this is the package of that model from json you provided with obfuscated keys |
@vladd-g, This is the expanded view for the package. ![]() But I can see something like this ![]() |
@ttnisal suppose |
HI @vladd-g, seems like it's not ![]() |
@ttnisal can you also try adding this?
|
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 obfuscated. And it opens up the paywall.
|
@ttnisal could you please send the obfuscated apk to [email protected]? Please also add the link to the issue in your email so that we know the context |
Hi @vladd-g, I have sent the email. Thanks |
@ttnisal thanks! |
@HermenegildoMI investigating |
@ttnisal @HermenegildoMI could you please also add the following line to the config? |
Hi @vladd-g . Thank you for the prompt response. I added When opening a Paywall view, the app crashes with the following logs: In code: const paywall = await adapty.getPaywall(paywallId);
if(paywall.hasViewConfiguration){
viewController = await createPaywallView(paywall);
await viewController.present();
} Adapty Logs before crashing: Note: actual id's were removed
App Crash Error:
![]() |
I got this weird issue where I only get the paywall pop up only in the first time I open up the app. If I close the app and open it I won't get it. I'm getting it only after reinstalling the app. This is on debug mode btw |
@ttnisal working on it |
@HermenegildoMI could you please provide full stacktrace of the crash itself? |
Here you go @vladd-g
|
@HermenegildoMI thank you! Do you experience it only in release mode, with |
Yes. That is correct. release mode, minify on. @vladd-g |
@HermenegildoMI but if you switch to debug or disable minifying, the issue is gone? just to make sure |
@vladd-g i was only able to open paywall view once and haven't been able to open it again since then in debug mode. I'm not sure that counts as working correctly. Very similar description to @ttnisal 's comments about debug mode. See quote below.
|
@HermenegildoMI @ttnisal could you please check these issues on v2.0.1? |
Hi @vladd-g, thanks for the update, seems like the pop-up appearing for only one time issue is still there. When trying to open it for the second time I got this logs
|
hi @ttnisal, could you please double-check that you don't call |
Hi @vladd-g , I double checked, seems like If I close the app without closing the paywall and restart it only I get the issue. If I close the paywall and close the app and start again I don't get any errors. Can see the paywall again. |
@ttnisal do the logs above match this case? or do you have new ones? |
@vladd-g I can send you new ones. Shall I email it to [email protected]? |
@ttnisal yes, thank you! please also add the link to the issue to your email |
@vladd-g, Sent the logs |
hi @ttnisal, could you please update to the |
I also have the issue with the view having shown once subsequently giving me the "AdaptyUIError.viewAlreadyPresented" error. I've gotta say, the docs on error codes etc. are really lacking |
hi @rennard, we'll review the docs, thank you for the report! |
For reference, it seemed like clearing the cache for the app and relaunching seemed to fix this. I believe it was due to hot reload crashing the app while the paywall was visible |
Description
Hi, We can subscribe to products and see paywalls in debug mode, But when we are on release mode the paywalls and functionalities are not working.
It gives the following error.
I have added the following configurations in proguard as well. But it doesn't seem to help
-keep class com.adapty.** { *; }
Adapty versions
Version
2.7.0
What platforms are you seeing the problem on?
Android
System info
The text was updated successfully, but these errors were encountered: