Code sign Android app for customers

Android App Bundle (AAB)

AAB is a new publishing format used to upload mobile apps to Google Playstore. This format includes all your app’s compiled code and resources, and defers APK generation and signing to Google Play. AAB is used to optimize the size of your mobile app, by allowing users to download the required assets or files based on their device specifications. 

 In Creator, we now support two file types for Android: 

• AAB - for publishing in Playstore.
• APK - for directly installing in your Android device.

Things to know

• You can code-sign your mobile apps using both AAB and APK file types by selecting both the options under the Export mobile app as section. Learn more

  

• When you choose to code-sign your apps using AAB, you can generate the APK as well from AAB. Learn more

There are two different keystore files needed to generate the appropriate file types:

• Upload Keystore file (for AAB)
• App Signing Keystore file (for APK)

Upload Keystore File

This is the second-level keystore file used to identify the developers who are responsible for their published apps. Users have to create this keystore file and use it while generating AAB. Learn how to generate upload keystore file

App Signing Keystore File

This is the main keystore file used to sign a mobile app to install them in your mobile and tablet devices. Users have to create this keystore file and use it while generating APK. Learn how to generate app signing keystore file

• Code sign using AAB
• Code sign using APK
• Code sign using AAB and APK
• Generate APK from AAB

Code sign Android app for customers using AAB

1. Edit your app. You'll be taken to your app's Design page.
2. Click Settings at the top of the Design page. You'll be taken to your app's Settings page.
3. Click Download as Mobile App under the Users and Control.
   ​
4. Click For Android under the For Customers section. The Download Mobile App pane will appear on the right.
   
5. Set App Icon as follows. This will be your app's icon on your users' mobile devices.
   • Use default icon will be selected by default. This is the application icon you set in the Settings page, as mentioned here.

   • You can opt to Upload Custom Icon, which needs to be a PNG file of 1024x1024 px resolution.

     

6. Enter Package Name. This will uniquely identify your Android app. It's usually in the format:

   com.companyname.appname.

   For example,

   com.zylker.employeemanagement.
7. In the Export Mobile App as section, tick the check box beside Android App Bundle (AAB).
8. Under the Upload Keystore Details, enter the required details. Refer to this page to know how to generate an app-signing keystore file.
9. Upload Keystore File.
10. Enter Keystore Password and the Key Password.

11. Enter Alias Name.

    

12. Under Push Notification, enter the required details. Firebase config file and Firebase Service Account file are required for enabling push notification support. Refer to this page to learn how to source them.
13. Upload Firebase config file.

14. Upload Firebase Service Account (FSA) file and click Generate Client.

    

15. Now, click Code sign. The codesign process can take up to 10 minutes.
    ​

    

16. View the code signing status under For Android.
17. Upon successful code signing, the status will change to Available and AAB will be generated.
    ​
18. Click the For Android button. The For Customers - Android pane will appear on the right.
19. Distribute your code-signed Android app to your users by the following method.

    • Click the Download AAB button in the Overview tab, then share the resulting Android App Bundle (.aab) file with your users.

      

    • You can also generate APK from here. Learn how
20. To disable the push notifications, click the Disable button beside the Push Notification section. 

21. Click OK in the Disable Push Notification for Android app popup.

    

22. To re-codesign your Android app, click the Re-codesign button at the top-right of the For Customers - Android pane.

    

23. Click OK in the Re-Codesign popup window.

Code sign Android app for customers using APK

1. Edit your app. You'll be taken to your app's Design page.
2. Click Settings at the top of the Design page. You'll be taken to your app's Settings page.

3. Click Download as Mobile App under Users and Control.

   

4. Click For Android under the For Customers section. The Download Mobile App pane will appear on the right.

   

5. Set App Icon as follows. This will be your app's icon in your users' mobile devices.
   • Use default icon will be selected by default. This is the application icon you set in the Settings page, as mentioned here
   • You can opt to Upload Custom Icon, which needs to be a PNG file of 1024x1024 px resolution.

6. Enter Package Name. This will uniquely identify your Android app. It's usually in the format:

   com.companyname.appname.

   For example,

   com.zylker.employeemanagement.
7. In the Export Mobile App as section, the check box beside Android Package (APK) will be selected by default.
8. Under the App Sign Keystore Details, enter the required details. Refer to this page to know how to generate an app-signing keystore file.
9. Upload Keystore File.
10. Enter Keystore Password and the Key Password.

11. Enter Alias Name.

    

12. Under Push Notification, enter the required details. Firebase config file and Firebase Service Account file are required for enabling push notification support. Refer to this page to learn how to source them.
13. Upload​ Firebase config file.

14. Upload Firebase Service Account file and click Generate client.

    

15. Now, click Code sign. The codesign process can take up to 10 minutes.

    ​

    ​

    

16. View the code signing status under For Android.

17. Upon successful code signing, the status will change to Available and APK will be generated.

    

18. Click the For Android button. The For Customers - Android pane will appear on the right.
19. Distribute your code-signed Android app to your users by the following method.

    • Click the Download AAB button in the Overview tab, then share the resulting Android Package Kit (.apk) file with your users.

      

20. To disable the push notifications, click the Disable button beside the Push Notification section. 

21. Click OK in the Disable Push Notification for Android app popup.

    

22. To re-codesign your Android app, click the Re-codesign button at the top-right of the For Customers - Android pane.

    

23. Click OK in the Re-Codesign popup window.

Code sign Android app for customers using AAB and APK

1. Edit your app. You'll be taken to your app's Design page.
2. Click Settings at the top of the Design page. You'll be taken to your app's Settings page.

3. Click Download as Mobile App under the Users and Control.

   

4. Click For Android under the For Customers section. The Download as Mobile App pane will appear on the right.

   

5. Set App Icon as follows. This will be your app's icon in your users' mobile devices.
   • Use Default Icon option will be selected by default. This is the application icon you set in the Settings page, as mentioned here
   • You can opt to Upload Custom Icon, which needs to be a PNG file of 1024x1024 px resolution.

6. Enter Package Name. This will uniquely identify your Android app. It's usually in the format:

   com.companyname.appname.

   For example,

   com.zylker.employeemanagement.
7. In the Export Mobile App as section, tick the check box beside Android App Bundle (AAB) and Android Package (APK).
   
8. Under the Upload Keystore Details, enter the required details.
9. Upload Keystore File. Refer to this page to know how to generate an app-signing keystore file.
10. Enter Keystore Password and the Key Password.

11. Enter Alias Name.

    

12. Under the App Sign Keystore Details, enter the required details.
13. Upload Keystore File. Refer to this page to know how to generate an app-signing keystore file.
14. Enter Keystore Password and the Key Password.
15. Enter Alias Name
16. Under Push Notification, enter the required details. The Firebase config file and Firebase Service Account file are required for enabling push notification support. Refer to this page to learn how to source them.
17. Upload Firebase config file.

18. Upload Firebase Service Account.

    ​

19. Click Code sign. The codesign process can take up to 10 minutes.

    

20. View the code signing status under For Android.

21. Upon successful code signing, the status will change to Available and AAB will be generated.

    

22. Click the For Android button. The For Customers - Android pane will appear on the right.
23. Distribute your code-signed Android app to your users by any of the following methods:

    • Click the Download AAB button in the Overview tab, then share the resulting Android App Bundle (.aab) file with your users.

      

    • Click the Generate APK button, then share the resulting Android Package Kit (.apk) file with your users. Learn how
24. To disable the push notifications, navigate to the For Customers - Android pane and click the Disable button beside the Push Notification section. 

25. Click OK in the Disable Push Notification for Android app popup.

    

26. To re-codesign your Android app, navigate to the For Customers - Android pane and click the Re-codesign button at the top-right.

    

27. Click OK in the Re-Codesign popup window.

Generate APK from AAB

Once AAB is generated, we can easily generate APK from it by using the App Signing keystore details.

To generate APK from AAB,

1. Click the For Android button. The For Customers - Android pane will appear on the right.

2. Click the Download AAB button in the Overview tab.

   ​

3. Enter the required details in the Generate APK popup and click Generate. The .apk file will be generated and you can share the resulting Android Package Kit (.apk) file with your users..

   

Points to Note

1. Declare foreground service information on Google Play Console:
   It is mandatory to declare foreground service information in the Play Console when uploading the AAB or APK application to the Google Play Console. To do so:
   • Create a screen recording that demonstrates the following steps in your codesigned app:
     1. Navigate to Settings > Offline Components > Add Components and download the preferred component.
     2. Return to the Offline Components section, where all downloaded components will be listed.
     3. Click the Sync icon next to the offline components.
        
        Refer below for a sample screen recording:
        
   • Upload the recorded video to Zoho Workdrive or Google Drive and generate an external share link. Learn how to generate an external share link for uploaded files in Zoho Workdrive
   • Follow these steps in the Google Play Console to declare foreground service information:
     1. Go to Google Play Console and navigate to App Content  > Foreground service permissions.
     2. Under Data sync, select Other in Network processing. Enter the external share link and click Save.