IssueTracker

You introduced this service: https://support.google.com/googleplay/android-developer/answer/7384423?hl=en for more secure certificate.

But it's a HELL!

1) you can't use CI (or you must change it at all), because you must signing apk with production key for Fabric
2) you must sign APK with production key for Samsung/Amazon store
3) you must sign with UPLOADING key for Google play store.

But ok, we can live with it. But we CAN'T live with this shit: DF-DLA-14
- We use old signing method (signing apk with production key)
-  User install version from Google Play
- User sign to Fabric beta releasing, install APK (without any issue, because it is signed with production key and have higher versionCode than Google play apk)
- we start using new Signign which use uploading key and signing with production key by Google Play
- user can't upgrade to new stable version from Google Play!!!! DF-DLA-14 Because you modify your APK in some cases and not just sign with production key!

When user use Samsung GalaxyApps store and install apk, after is new update in Google Play (and not in Samsung GalaxyApps) Google play start automatic update, but it everytime failed on DF-DLA-14 again!