Skip to content

Publish APK

Jump to bottom
Efra Espada edited this page Jan 3, 2020 · 8 revisions

Keys

- App signing key: The key used to sign the APK that's on a user's device. You currently hold the app signing key and use it to sign your APKs. When you complete the program sign-up flow you will upload this key to Google.

- Upload key (optional for existing apps): A new key you generate during your enrollment in the program. You should use the upload key to sign all future APKs prior to uploading them to the Play Console.

Source: Manage your app signing keys

The upload key is not valid for StringCare.

Option A: Using the signing key

Due to StringCare needs the final fingerprint, you must sign your APK with the signing key, not the upload key, which is more commonly used.

When the upload key is used, Google resigns the APK with the signing key before publishing it and StringCare won't be able to reveal the strings.

More information can be found in the Android Developers section Manage your own key and keystore.

Option B: Defining the signing key

You can define the SHA1 fingerprint used by Google for resigning your APK.

apply plugin: 'com.android.application'
apply plugin: StringCare

stringcare {
    mockedFingerprint = "A0:EA:C0:43:23:66:9B:C9:6B:A8:50:47:F5:18:B3:A3:52:C9:A4:3E"
}

License

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Home

Flutter Support

What Is StringCare

Implementation

Strings Usage

Assets Usage

Configuration

Publish APK

Limitations

Compatibility

Tasks

Resource Tips

Clone this wiki locally