Skip to main content

 

 

 

 
Language:
 
Applies only to Mobile Apps
Service Studio version:
 
 
OutSystems

Building apps with AndroidX

Template:OutSystems/Documentation_KB/ContentCollaboration
  • Edit
    Collaborate with us
    Edit this page on GitHub
  • AndroidX is a new and much improved Android support library. The Android developers no longer maintain Support Library after Android 9.0 (API level 28). This document shows how to create native builds with AndroidX.

    To build your apps and custom mobile plugins with AndroidX, you need to be using MABS 6.3 Beta or later. MABS releases after 6.3 Beta have AndroidX enabled by default.

    With AndroidX support, MABS replaces the legacy dependencies from Support Library with the corresponding dependencies from the new AndroidX library. This migration is necessary because Support Libraries and AndroidX packages can't be in the same Android project.

    You should test your apps and make sure that all features are working as expected. Testing is particularly relevant for the features that depend on Support Library, such as custom Cordova plugins.

    For more information about AndroidX migration check out Migrating to AndroidX and Migrating to AndroidX: tips, tricks, and guidance by Android Developers.

    The content in this document applies only to the native Android apps.

    How to enable AndroidX

    You need to enable AndoridX if you're using MABS 6.3 Beta. AndoridX is enabled by default in MABS 7 Beta.

    To build a mobile app with AndroidX enabled, do the following:

    1. Open your mobile app in Service Studio.

    2. Open the main module of the app. You need to open the main module because MABS ignores the AndroidX setting in a dependency module.

    3. Go to the mobile properties and edit the Extensibility Configurations. Add a new key-value pair in the android section, and set AndroidXEnabled to true.

      {
          "preferences": {
              "android": [{
                  "name": "AndroidXEnabled",
                  "value": "true"
              }]
          }
      }
      
    4. Publish the app in your environment so MABS can acquire the updated resources.

    5. Create native mobile builds of the app.

    • Was this article helpful?