# Credentials

The **Credentials** tab, located within the **Settings** section of Project, allows you to securely upload and manage all required certificates, keys, and provisioning profiles for your mobile applications. Proper credential management is essential for successful build processes, platform compliance, and secure distribution across **iOS**, **Android**, and **Huawei** ecosystems.

<figure><img src="/files/ARmUPVvLSSDrRk7po6Di" alt=""><figcaption></figcaption></figure>

## <mark style="color:red;">iOS Credentials</mark>

iOS applications require a set of mandatory and optional credentials, including separate credentials for **Extensions** if used.

{% hint style="danger" %}
The App Maker platform monitors expiration dates and alerts users in red to prevent disruptions during the build or release process.
{% endhint %}

<figure><img src="/files/db0NbcMCz8viVsfvT6Rj" alt=""><figcaption></figcaption></figure>

### <mark style="color:red;">**Distribution Certificate**</mark>

An **Apple Distribution Certificate** is required to sign and distribute iOS, iPadOS, tvOS, watchOS, and certain macOS apps.

* It is issued by Apple via the Developer portal.
* The certificate ensures that your app is from a trusted source and meets Apple’s security policies.

📎 [More information on Apple Certificates → Apple Developer Support](https://developer.apple.com/support/certificates/)

### <mark style="color:red;">**Certificate Password (Private Key)**</mark>

The **Private Key** associated with your Apple Distribution Certificate is used to digitally sign your application.

* Must be uploaded along with the certificate file.
* The password is required to unlock the private key during the build process.

### <mark style="color:red;">**APN Certificate**</mark>

The **Apple Push Notification service (APNs) Certificate** is necessary to enable push notifications for your iOS app.

* Enables secure communication with Apple’s push notification servers.
* Expired APNs certificates will block notification delivery.

### <mark style="color:red;">**APN Certificate Key**</mark>

This is the private key corresponding to the APNs certificate.

* Enables the App Maker to send push notifications on behalf of your app.

### <mark style="color:red;">Provisioning</mark> <mark style="color:red;">**Profile**</mark>

The **Provisioning Profile** links your Apple Developer account, the target devices, and the entitlements required by your app.

* Required to run the app on physical devices and distribute it via the App Store.

{% hint style="warning" %}
App Maker automatically monitors expiration dates and notifies users.
{% endhint %}

### <mark style="color:red;">Extension Profiles</mark>

If your iOS app includes **native extensions** (e.g., notification service extensions or app clips), a separate provisioning profile must be uploaded for each extension.

📎 [How to Create a Provisioning Profile → Apple Developer Documentation](https://developer.apple.com/documentation)

## <mark style="color:red;">Android / Huawei Credentials</mark>

For Android and Huawei-compatible apps, credentials revolve around securely signing APK or AAB builds using a **keystore file** and associated secrets.

<figure><img src="/files/Uee0scjjxjRWCorGeUpV" alt=""><figcaption></figcaption></figure>

### <mark style="color:red;">**Key Alias**</mark>

The **Key Alias** is a label for a specific key inside the keystore file.

* Each alias corresponds to a key pair (public/private).
* It must match the alias used during app signing.

### <mark style="color:red;">**Key Password**</mark>

This password protects the private key linked to the key alias.

* Needed during the signing process.
* Losing this password will prevent future updates of your app.

Key password is the specific password that protects the private key associated with that alias, enabling its use for operations like app signing.

### <mark style="color:red;">**Keystore File**</mark>

A **keystore file** (typically `.jks` or `.keystore`) is a secure container for your cryptographic keys and certificates.

* Required for signing Android/Huawei builds.
* Must be uploaded to App Maker to enable build processes.

📎 [How to Create a Keystore File → Android Developer Guide](https://developer.android.com/studio/publish/app-signing)

### <mark style="color:red;">**Keystore Password**</mark>

The **Keystore Password** protects access to the entire keystore file.

{% hint style="danger" %}
**Critical Note:** Losing your keystore password means losing access to your app’s signing key. This would prevent you from publishing updates to your app on Google Play or Huawei AppGallery. In such a case, you would be forced to publish a brand-new app, losing your current users and ratings. Always store your keystore credentials in a secure, backed-up location.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.akinon.com/tutorials/app-maker/projects/settings/credentials.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.