# Rebranding Sisense Mobile > Sisense enables you to provide your users with a fully white-labeled version of Sisense Mobile that matches your brand's look and feel. *Source: https://docs.sisense.com/main/SisenseLinux/rebranding-sisense-mobile.htm* --- Last updated: June 11, 2026 | | | | --- | --- | | [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) | | Grow    Enterprise | Cloud     On-Prem | Sisense enables you to provide your users with a fully white-labeled version of Sisense Mobile that matches your brand's look and feel. ![8 7rebrandmobilethumb](https://docs.sisense.com/main/Resources/Images/8-7rebrandmobilethumb0300.png) ![8 7rebranded loginthumb](https://docs.sisense.com/main/Resources/Images/8-7rebranded-loginthumb0300.png) ![8-7displaynamethumb0300.png](https://docs.sisense.com/main/Resources/Images/8-7displaynamethumb0300.png) ![8 7acmealertthumb](https://docs.sisense.com/main/Resources/Images/8-7acmealertthumb0300.png) The following objects can be rebranded: - App icon and title - Splash screen - Mobile notification logo image and colors - Mobile color palette - App description and information that appears in the app store Rebranding Sisense Mobile is a premium Sisense offering. Contact your Sisense representative. ## Sisense Mobile Rebranding Process Once you have purchased a rebranded version of Sisense Mobile, complete this [form](https://assets-validation.sisense.com/), which details all the information and resources you must provide to Sisense. Examples of resources are: - Icons in different sizes (iPhone, Android) - Specific colors - Mobile app name - Other configurable options within Sisense Mobile. A detailed description of each required resource and field is included in the checklist. **Important:** Zip these resource files together, and send the zipped file and your completed checklist to [rebranded\_mobile@sisense.com](mailto:rebranded_mobile@sisense.com), with your Sisense representative copied on the email. Sisense will create a rebranded mobile app and provide you with a version to try out. The white-labeled mobile app will be fully tested by Sisense QA, but Sisense recommends that you test it for yourself before uploading it to the app stores. Sisense will provide instructions for signing the application and uploading it to the app stores. Once Sisense validates that all resources are accounted for and are correct, the rebranding Sisense mobile process typically takes up to one month. ## Publishing Your App **Note:** It is your responsibility to publish your application. Use the information in this section to help you do so. Before Sisense provides you with your rebranded mobile app, Sisense signs the app for you. Both the Google Play Store and the Apple App Store require that all apps are digitally signed with a certificate. Therefore, you must provide Sisense with the relevant certificates as described below. Sisense then returns the signed app to you and you can publish the app in the Google Play Store (Android) or in the Apple App Store (iOS). For instructions on how to publish, see Resources for Publishing Your Application . ## Generating Signing Certificates ### Android **Signing Your App** - For instructions on signing your rebranded Android-based mobile app, see [Sign your app](https://developer.android.com/studio/publish/app-signing). **Notes:** - The Android certificate should be in the form of a JKS file. - You must provide all passwords for Keystore (and for the key, if it was set). To create and check the key, and to make sure that the password is correct, go [to keystore-explorer](https://keystore-explorer.org/downloads.html). **Important:** When configuring the expected lifespan of your app, it is recommended to set a validity period of 25 years or more. When your key's validity period expires, users will no longer be able to seamlessly upgrade to new versions of your app. - Google Play App Signing: If you plan to publish your apps on Google Play, the key you use to sign those APKs must have a validity period ending after 22 October 2033. Google Play enforces this requirement to ensure that users can seamlessly upgrade apps when new versions are available. If you use Google Play App Signing, Google ensures your apps are correctly signed and able to receive updates throughout their lifespans. - More information: - [Keystore Explorer User Manual](https://keystore-explorer.org/doc/5.4/keyStoreManagement.html) - [Google Play App Signing](https://developer.android.com/studio/publish/app-signing) ### iOS 1. Go to [https://developer.apple.com](https://developer.apple.com/) and create an identifier (App ID) for the new app. 2. If you do not have an iOS distribution certificate, create one. See the instructions below. 3. Download the certificate to the Mac that has your private key, and add it to the key chain (double click). 4. Open **Keychain Access** on your Mac, and under **My Certificates** locate the iPhone Distribution Certificate you have created for the app. 5. Select **File > Export Item** . Make sure the file format is p12. 6. In [developer.apple.com](http://developer.apple.com/), create a Distribution Provisioning Profile for your app, using the same certificate you created above. 7. Download the certificate to your Mac. 8. Double click the certificate. This will start the process to install it. For more information, see [Code Signing](https://developer.apple.com/support/code-signing). ### Creating a Certificate for the Apple App Store You need to create a p12 certificate to publish an application on the Apple App Store. There are three main steps in this procedure: 1. Create a .certSigningRequest (CSR) file 2. Create the .cer file 3. Install the .cer file and generate a .p12 certificate These steps are detailed below. **Note:** Before performing this procedure, make sure you have registered in the iOS Developer Program. 1. **Create a .certSigningRequest (CSR) File** 1. From **Utilities** or the **Launchpad**, search for and open **Keychain Access**. ![8 7keychain access](https://docs.sisense.com/main/Resources/Images/8-7keychain-access.png) ![8 7keychain access](https://docs.sisense.com/main/Resources/Images/8-7keychain-access-2.png) 2. From the Keychain Access toolbar, select **Keychain Access > Preferences**. 3. Click the **Certificates** tab. 4. Set both **Online Certificate Status Protocol** and **Certificate Revocation List to Off**. 5. Close the window. 6. From the toolbar, open **Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority**. ![8 7keychain request cert](https://docs.sisense.com/main/Resources/Images/8-7keychain-request-cert.png) 7. Enter the email address and common name that you used to register in the iOS Developer Program. 8. Leave the CA Email field empty and select **Saved to disk and Let me specify key pair information**. 9. Click **Continue**. 10. Select a filename and destination on your local computer. 11. Click **Save**. 12. Set the Key Size value to **2048 bits**. 13. Set Algorithm to **RSA**. 14. Click **Continue**. This creates and saves your certSigningRequest file (CSR) to your local computer. A public and private key is also installed in Keychain Access with the Common Name entered. 2. **Create a .cer File in Your iOS Developer Account** 1. Go to and sign in to your Apple Developer Account. 2. Click **Certificates, Identifiers & Profiles**. 3. Click **Add +** at the top-right of the main panel. 4. Select **Apple Distribution**. 5. Click **Continue**. ![8 7apple distribution](https://docs.sisense.com/main/Resources/Images/8-7apple-distribution.png) 6. Click **Choose File** and locate the CSR file on your local machine that you created in the first stage of this procedure. 7. Click **Generate**. 8. Click **Download** to download the file. 9. Click **Provisioning Profiles**. ![8 7apple profilesthumb](https://docs.sisense.com/main/Resources/Images/8-7apple-profilesthumb0300.png) 10. Under **Distribution**, select **App Store** and click **Continue**. ![8 7apple app storethumb](https://docs.sisense.com/main/Resources/Images/8-7apple-app-storethumb0300.png) 11. In the dropdown, select the relevant app ID, and click **Continue**. If multiple certificates are shown, make sure to select the correct one. ![8 7apple select appid](https://docs.sisense.com/main/Resources/Images/8-7apple-select-appid.png) 12. Check that the expiration date matches. This is important in case you want to export \*.p12 Distribution certificates from Keychain. ![8 7apple check exp datethumb](https://docs.sisense.com/main/Resources/Images/8-7apple-check-exp-datethumb0300.png) ![8 7apple check exp date](https://docs.sisense.com/main/Resources/Images/8-7apple-check-exp-date2.png) 13. Click **Download** to save your provision file. 3. **Install .cer and Generate a .p12 Certificate:** 1. Open **Keychain Access** and go to: **Default Keychains > login > My Certificates** or **Certificates**. 2. Locate the .cer file you downloaded in the previous stage and double-click it or drag & drop it to **My Certificates** or **Certificates**. 3. Set the **Login** dropdown to **login** and click **Add**. 4. Open **Keychain Access** and locate the profile created in the first stage of this procedure. **Important:** Make sure that the certificate is 'trusted' and 'valid'. If not, you will not be able to export it in p12 format. ![Image 20220930](https://docs.sisense.com/main/Resources/Images/image-20220930-193632_750x181.png) The **Distribution Certificate (\*.cer)** should be installed in the same Keychain, on the same Mac, under the same account, where **CertificateSigningRequest.certSigningRequest** was created and where the **private key is located**. You should be able to expand the Apple Distribution certificate after installation to Keychain and see the private key inside. You need the private key that corresponds to the certificate. Without that, you cannot create a .p12 file or use the certificate to sign your app. **The private key is not included in a .cer file**, and it is impractical to compute it from anything in the .cer file. The private key was created when you created the certificate - it is located in the keychain on the computer on which you created the certificate. If it has been deleted or lost, you will need to create a new signing identity. From Apple's article on [Maintaining Your Signing Identities and Certificates](https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html). A .p12 file is a good form of backup, since it includes both the private key and the certificate (which includes the public key). However, if you have lost the private key and do not have a backup, it cannot be retrieved, and you start over. 5. Expand the private key profile to display the certificate you added. 6. Select the private key and the certificate. **Do not select the public key**. 7. Right-click the selection and select **Export 2 items**. 8. Make sure that the file format is .p12 and enter a filename and destination on your local computer. 9. Click **Save**. 10. Set a password and click **OK**. 4. **Upload the .p12 Certificate to FireBase** 1. Navigate to . 2. Click **Add a project**. ![8-7firebase-add-project.png](https://docs.sisense.com/main/Resources/Images/8-7firebase-add-project.png) 3. Add the following details: 1. Project name 2. iOS bundle ID - The same as you mentioned in the [Sisense Mobile Checklist](https://docs.sisense.com/main/Resources/Images/Sisense_Mobile_Checklist_launchStoryboard.docx). ![8 7firebase registerthumb](https://docs.sisense.com/main/Resources/Images/8-7firebase-registerthumb0300.png) 3. App Store ID. You can find your App Store ID in your app's URL. In the following example, the App Store ID is 123456789: `https://itunes.apple.com/us/app/yourapp/id123456789` 4. Add your Android and/or iOS apps and check if all configurations are set correctly. 5. When you have uploaded your Development APNs certificate and have configured all the settings, download the .plist file. ![8 7downdload plist](https://docs.sisense.com/main/Resources/Images/8-7downdload-plist.png) 5. **To enable sending push notifications:** 1. Create an Auth Key or Certificate in the Apple Developer Member Center 2. **Create the Authentication Key (preferred method, as it never expires):** Generate an authentication key for an App ID enabled for push notifications. If you have an existing key, you can use that key instead of generating a new one. 1. In your developer account, navigate to **Certificates, Identifiers & Profiles**. 2. In the Keys section, select All. ![8 7apple keys](https://docs.sisense.com/main/Resources/Images/8-7apple-keys.png) 3. In the upper-right corner, click **Add +**. 4. Enter APNs Auth Key description. 5. Under **Key Services**, select the APNs checkbox and click **Continue**. 6. Click **Confirm** and then **Download**. **Important:** Save your key in a secure place. This is a one-time download and the key cannot be retrieved later. ![8 7apple test push notification](https://docs.sisense.com/main/Resources/Images/8-7apple-test-push-notification.png) 7. Navigate to . 8. Click **Settings > Cloud Messaging > iOS App Configuration > APNs Authentication Key**. 9. In the APNs Authentication Key select your .p8 file. 10. To verify that your APN's authentication key is set up properly and is accepted by APNs, send a test push notification. 6. **Create a Certificate (Optional):** **Note:** **You must recreate the certificate every year.** 1. Navigate to . 2. In the **Certificates, Identifiers and Profiles** page, click **Certificates > Add**. ![8 7add certificates](https://docs.sisense.com/main/Resources/Images/8-7add-certificates.png) You can now use one certificate for both the sandbox and production environment. ![Apple push notifications](https://docs.sisense.com/main/Resources/Images/apple-push-notifications.png) ![8 7apple downloadthumb](https://docs.sisense.com/main/Resources/Images/8-7apple-downloadthumb0300.png) 3. Install the .cer and export the .p12 with keystore in the same way as was done when signing the certificate. 4. Navigate to https://console.firebase.google.com/u/0/project/YOUR\_PROJECT\_NAME. 5. Click **Settings > Cloud Messaging > iOS App Configuration > APNs Certificate**. 6. In the Upload your Development APNs certificate section, upload your .p12 file. ## Sisense Mobile Upgrades Sisense regularly releases updates for Sisense Mobile. Sisense will periodically (about once a quarter) notify you when an upgraded rebranded version is available, and you can choose whether to upload the app to your store or not. To apply the upgrade, you might need to regenerate certificates, based on their expiration date. Sisense performs a full QA cycle on all upgrades, but recommends that you test every version of your application before publishing. For instructions on how to publish see the following section, Resources for Publishing Your Application. Contact us at [rebranded\_mobile@sisense.com](mailto:rebranded_mobile@sisense.com) for any technical questions related to this process. ## Resources for Publishing Your Application Use these resources to help you learn how to publish and republish your application: **Android \*.apk** - **IOS \*.ipa** - [https://developer.apple.com/app-store/review/guidelines/](https://developer.apple.com/app-store/review/guidelines) - **Loading the \*.ipa file without TestFlight** -