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.
iOS Credentials
iOS applications require a set of mandatory and optional credentials, including separate credentials for Extensions if used.
The App Maker platform monitors expiration dates and alerts users in red to prevent disruptions during the build or release process.
Distribution Certificate
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
Certificate Password (Private Key)
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.
APN Certificate
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.
APN Certificate Key
This is the private key corresponding to the APNs certificate.
Enables the App Maker to send push notifications on behalf of your app.
Provisioning Profile
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.
App Maker automatically monitors expiration dates and notifies users.
Extension Profiles
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
Android / Huawei Credentials
For Android and Huawei-compatible apps, credentials revolve around securely signing APK or AAB builds using a keystore file and associated secrets.
Key Alias
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.
Key Password
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.
Keystore File
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
Keystore Password
The Keystore Password protects access to the entire keystore file.
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.
Last updated
Was this helpful?