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
Distribute.setEnabled(false) has no effect for non debuggable builds #1208
Comments
Hi, For release builds from the store we use an automatic store detection, that's probably what failed in your case and to troubleshoot that we will need the verbose logs of the SDK. For example have 1 of the release build use As for why |
Hi @guperrot , Thank you for the answer. My question refers mainly to the
It is clearly a case of wrong usage from my side. However, there is absolutely no mention in any documentation that order of operations is important. The examples for I would like to give you an extra feedback from my side. In my opinion, everything related to debuggable or non-debuggable builds should not be of any concern to the any SDK. If such information is needed, it should be just configurable through flags upfront. Any decision depending on the type of the build should be made exclusively by the developer of the app and not hidden inside the code of any third party SDK. Otherwise our builds become extremely unpredictable. |
Hey, @luboganev, you are correct. |
We will need to update the docs for how to use those APIs. As for some context, Then recently we had the community contribution Though the methods have similar names they are indeed very different in nature and sorry for the confusion, I agree that the docs need to be improved. As for the original issue it does not seem to be resolved as we are detecting the store automatically and should not have open the browser if installed from Google Play. I'm still curious about that one if you have time to test on an alpha build with debug logging (from AppCenter SDK) enabled. |
Hi, Thank you for the detailed information. I understand the big picture now. The goals of the SDK make sense, but most of the times one needs to do complete configuration themselves. I guess that is something we are used to, that's why I expected I need to do the configuration. About the original issue, I haven't installed the app straight from Google Play. I just tested locally the APK we have prepared for the release by sideloading it on our test devices. We don't use the Alpha and Beta channels of Google Play, that's what we used Hockey and now AppCenter for. So I'm certain that the behavior when installing from Google Play works the way you describe it. Unfortunately I don't have time now to test it but it is good to know that the SDK behaves is like that. However, the fact I had no clue about that shows that maybe this nice feature should be highlighted a bit more in the documentation as well. |
Ok, so I was confused all along by the fact that you said that opening the app from Google Play opened the browser, but actually it was sideloaded. Then it's expected behavior to open browser if not installed from Google Play and then no need for extra testing. So basically we need to clarify the documentation. |
Small update here - docs are updated now, and info about those 2 added |
Description
I'm running the AppCenter Distribute normally only for non-production builds to distribute internally and I want it disabled when I upload to Google Play. I have setup the setEnabled and setEnabledForDebuggableBuild both to false in this order. Despite of that my Google Play Live Production app suddenly started opening the AppCenter in the browser every time I start it.
Repro Steps
Distribute.setEnabled(false); Distribute.setEnabledForDebuggableBuild(false); AppCenter.start(this, "<my appcenter id>", Crashes.class, Analytics.class, Distribute.class);
Details
AppCenter.setLogLevel(Log.VERBOSE)
before your call toAppCenter.start(...)
and include the logs here:I cannot do that, the issue happens on non-debuggable builds, so I cannot see any log messages.
My currrent workaround:
The only way to make sure I don't get this wrong behavior is by no including the Distribute.class at all when starting AppCenter SDK.
The text was updated successfully, but these errors were encountered: