I know this is old question, but future references. In Android Studio with Gradle: buildTypes { release { debuggable true minifyEnabled true proguardFiles getDefaultProguardFile(‘proguard-android.txt’), ‘proguard-rules.txt’ } } The line debuggable true was the trick for me. Before Gradle 1.0 it was runProguard instead of minifyEnabled. Look at here.
The easiest way is using adb. You don’t have to write any code. Just run in a terminal: adb shell am broadcast -a com.android.vending.INSTALL_REFERRER -n <your.package>/.<path.up.until.your.BroadcastReceiver> –es “referrer” “utm_source=test_source\&utm_medium=test_medium\&utm_term=test_term\&utm_content=test_content\&utm_campaign=test_name” Here’s my exact line: am broadcast -a com.android.vending.INSTALL_REFERRER -n net.lp.collectionista/.util.broadcast_receivers.FacadeBroadcastReceiver –es “referrer” “utm_source=test_source\&utm_medium=test_medium\&utm_term=test_term\&utm_content=test_content\&utm_campaign=test_name” But your BroadcastReceiver may need to be the AnalyticsReceiver, i.e. For Google Analytics … Read more
At last adding a special case for Nexus 7 with in <compatible-screens> tag worked for me. As Nexus 7 has tvdpi density <compatible-screens> <!–no small size screens –> <!–all normal size screens –> <screen android:screenSize=”normal” android:screenDensity=”ldpi” /> <screen android:screenSize=”normal” android:screenDensity=”mdpi” /> <screen android:screenSize=”normal” android:screenDensity=”hdpi” /> <screen android:screenSize=”normal” android:screenDensity=”xhdpi” /> <!– all large size screens –> … Read more
To properly handle SSL certificate validation, change your code to invoke SslErrorHandler.proceed() whenever the certificate presented by the server meets your expectations, and invoke SslErrorHandler.cancel() otherwise. As email said, onReceivedSslError should handle user is going to a page with invalid cert, such like a notify dialog. You should not proceed it directly. For example, I … Read more
Reference Link android:versionCode An internal version number. This number is used only to determine whether one version is more recent than another, with higher numbers indicating more recent versions. This is not the version number shown to users; that number is set by the versionName attribute. The value must be set as an integer, such … Read more
The error suggests that you have uploaded an APK or an App Bundle previously. All the artifacts you upload to the Play Console should all be signed with the same keystore. So the error means that you signed the App Bundle with a key that is different than the ones you have uploaded previously. You … Read more
This happened to me when I published two APKs (versions 3 and then 4) in a short space of time. Clicking “Deactivate” on the dropdown next to version 3 appeared to fix it. My guess is that this is a very-poorly-worded error message meaning something like “your original APK hasn’t been published to all the … Read more
There’s no way to recover your key. I once accidently deleted mine and faced the same problem. I ended up emailing the few users who had already purchased my app about my mistake and told them to let me know who they are and that I would refund their purchase of the app again, if … Read more
I’ve contacted Google Play support: UPDATE 2 : UPDATE 1 : Problem solved guys,Google play finally fix their problem by sending an update of (Google Play Libraries), so you don’t need to do anything. if you still seeing the UPDATE button,just clear the cache of Google Play from setting.
You don’t need to filter your app based on device/manufacturer in the application code, instead you can do it from the android market developer console – https://market.android.com/publish/ just when you publish the app itself. There is a ‘Supported Devices’ section on the developer console, which shows you a list of all the devices which can … Read more