Specific version (select from list): Generate mobile app packages (in the current environment) with the MABS version selected from the list. When choosing a MABS version you have the following options available:Īlways use the latest version available: Always use the most recent MABS version available to generate the mobile package of the app for the current platform and in the current environment. Note: The MABS version selection is only available for apps whose native platform settings are already configured.Ĭlick Save and Generate and wait a few moments while OutSystems generates your mobile app package.
In the Settings column, click the Configure link for the iOS or Android entry.Īt the end of the configuration settings page, select the MABS version you wish to use for generating the mobile app package for the mobile platform you're configuring (iOS or Android) in the current environment, either the latest available version or a specific version (see below for details).
The native mobile settings are in the Native Platforms section. In Service Center, click the Applications tab, open your mobile app from the app list and select the Distribute tab. To choose a MABS version do the following: You can do this in Service Center at the app level. You can select the MABS version used to generate the mobile packages by mobile app and by mobile platform (iOS and Android), for a given environment. However, you might not want to use the latest version, since different MABS versions support different mobile stacks and therefore different ranges of devices and mobile platform versions. MABS is continuously improved and OutSystems regularly makes available new versions of this cloud service. The Mobile Apps Build Service (MABS) is a cloud service used by OutSystems to generate the mobile packages of your mobile apps developed in OutSystems for iOS and Android.
The next time you generate a new app package, the version code increments by one.Ĭhoosing the MABS version to build your mobile packages In the Distribute tab, under the section Native Platforms, click the Change link in the Code column for the iOS or Android entry.Įnter the new code for the mobile app and click Apply.
To set a different version code for your mobile app, do the following: In this case, you can set the version code of your OutSystems mobile app to a different value. For example, if you are migrating an existing mobile app from another technology provider to OutSystems, the current version code of your app in the app store is higher than the first OutSystems app version code. See more detailed information in Android and iOS documentation.īy default, OutSystems increments the version code by one every time the MABS generates the mobile app package.įor some cases, you might need to change the default mobile app version code. App stores use this number to determine whether one version is more recent than another. The mobile app version code is an internal number associated with the generation of the mobile app package. Follow the configuration steps for your desired scenario, described in the topics listed at the end of this page.Īfter defining or changing your mobile app iOS or Android settings, click Save.Īt the end of the configuration settings page, select the MABS version you wish to use for generating the mobile app package for the mobile platform you're configuring (iOS or Android) in the current environment. To configure your mobile app package for the first time or to change the current configuration for a given platform (iOS or Android), click the Configure link for the iOS or Android entry. Open the Service Center console of the environment ( and navigate to Factory.Ĭlick the Applications tab, open your mobile app from the app list, then select the Distribute tab. To configure or generate your mobile app package (iOS or Android) in Service Center, do the following:
This archive contains the three builds used by PCem - XT, AT, and AT v1.1.5 (used by PS/1 Model 2011).Configure and generate a mobile app package in Service Center The XTIDE Universal BIOS is licensed under the GPLv2. There appears to be no copyright on this BIOS at all so I have no issues with distributing it. Useful downloads : Generic clone XT BIOS ROMs
PCem v17 for Linux Old versions : PCem v16 for Windows