<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Taner Gedikoğlu on Medium]]></title>
        <description><![CDATA[Stories by Taner Gedikoğlu on Medium]]></description>
        <link>https://medium.com/@tanergedikoglu?source=rss-7955f5494423------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JQz-fgRAxMlN4m30k-Tk_A.jpeg</url>
            <title>Stories by Taner Gedikoğlu on Medium</title>
            <link>https://medium.com/@tanergedikoglu?source=rss-7955f5494423------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:02:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tanergedikoglu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[App Center Ends Support — Here’s Your Azure DevOps Pipeline for Mendix Native App Deployment]]></title>
            <link>https://medium.com/mx-experts/app-center-ends-support-heres-your-azure-devops-pipeline-for-mendix-native-app-deployment-601046ef2913?source=rss-7955f5494423------2</link>
            <guid isPermaLink="false">https://medium.com/p/601046ef2913</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Taner Gedikoğlu]]></dc:creator>
            <pubDate>Fri, 07 Mar 2025 14:34:53 GMT</pubDate>
            <atom:updated>2025-03-10T09:04:56.710Z</atom:updated>
            <content:encoded><![CDATA[<h3>App Center Ends Support — Here’s Your Azure DevOps Pipeline for Mendix Native App Deployment</h3><p>With Microsoft discontinuing App Center support on March 31, this blog shows how to automate Mendix native mobile builds for Android and iOS using Azure DevOps. This solution is ideal for Mendix projects that can’t or don’t want to rely on cloud-based CI/CD services like Bitrise, prefer using Azure DevOps cloud, or require an on-premise approach. The complete pipeline script is available as a <a href="https://gist.github.com/tanerg/ea5fbcccfeeb01953e5ed4919c6be20c">Gist here</a>.</p><h3>Introduction</h3><p>Microsoft is discontinuing App Center support on March 31, affecting many Mendix developers who currently rely on it. Recognizing this challenge, I developed a reliable and efficient pipeline directly from my own Mendix projects using Azure DevOps. This solution is especially beneficial for projects unable or unwilling to use cloud-based CI/CD tools like Bitrise, prefer using Azure DevOps cloud, or require an on-premise approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hIR24Umo3Qv6D9JHH_qpWQ.png" /></figure><h3>Prerequisites</h3><ul><li>A Mendix native project ready for deployment</li><li>An Azure DevOps environment (cloud or on-premise) with macOS and Ubuntu agents</li><li>Access to Google Play Console and Apple App Store Connect</li><li>Certificates, provisioning profiles, keystore files, and other secure credentials</li></ul><h3>Pipeline Structure Overview</h3><p>This blog demonstrates a multi-stage pipeline consisting of:</p><ol><li><strong>Stage 1:</strong> Building Mendix native bundles.</li><li><strong>Stage 2 and 3 (parallel stages):</strong></li></ol><ul><li>Android package build</li><li>iOS package build</li></ul><p>The first stage generates the native bundles, after which the two subsequent stages run concurrently, independently creating Android and iOS packages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*EKdQY70TeLlvzaqyTDQfIg.png" /><figcaption>Multi stage pipeline</figcaption></figure><h3>Step-by-Step Guide</h3><h4>1. Preparing and Bundling Your Mendix Application</h4><p>Before we can start building the mobile packages, we first need to bundle our Mendix App as outlined in <a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally-manually/#bundling-your-mendix-app">Mendix documentation</a>. Bundling essentially creates JavaScript files specifically tailored for each platform (Android and iOS).</p><p><strong>Steps summary:</strong></p><ul><li>Set up pipeline naming and variables</li><li>Downloading MxBuild</li><li>Extracting and setting up MxBuild</li><li>Building Mendix native bundles using MxBuild</li><li>Publishing generated bundles as pipeline artifacts for subsequent stages</li></ul><pre>trigger: none<br><br># Name of the pipeline - this is what will be displayed in the UI when you run the pipeline<br># $(Year:yy) - Two-digit year<br># $(DayOfYear) - Day of the year<br># $(rev:.r) - Auto-incremented revision number<br>name: $(Year:yy)$(DayOfYear)$(rev:.r)<br><br>variables:<br>  # This is the version of the Mendix Native Template to use<br>  # https://github.com/mendix/native-template<br>  nativeTemplateVersion: &quot;11.x.x&quot;<br>  # This is an incrementing counter we will use to generate a unique version code for each build<br>  versionCode: $[ counter(&#39;versionCodeCounter&#39;, 1) ]<br>  buildNumber: $(versionCode)<br>  # This is the version of the Mendix MxBuild to use<br>  # https://docs.mendix.com/refguide/mxbuild/<br>  mxversion: &quot;10.18.0.54340&quot;<br><br>stages:<br>  - stage: build_bundles<br>    displayName: &quot;Build Mendix Bundles for iOS and Android&quot;<br>    jobs:<br>      - job: Build<br>        displayName: &quot;Build Mendix Bundles for iOS and Android&quot;<br>        pool:<br>          vmImage: &quot;ubuntu-latest&quot;<br><br>        steps:<br>          - task: CmdLine@2<br>            displayName: &#39;Display Version Code&#39;<br>            inputs:<br>              script: |<br>                echo &quot;Version Code: $(versionCode)&quot;<br><br>          # Download the Mendix MxBuild from Azure Blob Storage I prefer to store the mxbuilds in an Azure Blob Storage for speed<br>          # you can also download it from the Mendix website as explained here https://docs.mendix.com/refguide/mxbuild/<br>          - task: AzureCLI@1<br>            displayName: Download MxBuild<br>            inputs:<br>              AzureSubscription: &quot;Azure Inventara Resources&quot;<br>              scriptLocation: inlineScript<br>              inlineScript: |<br>                az storage blob download --container-name mendix --file $(Agent.TempDirectory)/mxbuild-$(mxversion).tar.gz --name mxbuild-$(mxversion).tar.gz --account-key $(storage-accountkey) --account-name $(storage-accountname)<br><br>          # Extract the downloaded MxBuild into the Tools directory<br>          - task: ExtractFiles@1<br>            displayName: Extract MxBuild<br>            inputs:<br>              archiveFilePatterns: $(Agent.TempDirectory)/mxbuild-$(mxversion).tar.gz<br>              destinationFolder: $(Agent.ToolsDirectory)/mxbuild<br>              cleanDestinationFolder: false<br>              overwriteExistingFiles: true<br><br>          # Locations of java can be different on different agents see https://github.com/actions/runner-images/tree/main/images<br>          - task: CmdLine@2<br>            displayName: &quot;Perform MxBuild to generate the bundles for the native mobile app&quot;<br>            inputs:<br>              script: &#39;./mxbuild --target=deploy --native-packager --loose-version-check --java-home=$JAVA_HOME_21_X64 --java-exe-path=$JAVA_HOME_21_X64/bin/java --write-errors=$(Build.ArtifactStagingDirectory)/mxbuild-errors.json &quot;$(Build.SourcesDirectory)/Mobile.mpr&quot;&#39;<br>              workingDirectory: &quot;$(Agent.ToolsDirectory)/mxbuild/modeler&quot;<br><br>          # Publish the generated bundles as a pipeline artifact so that we can download them in the next stages<br>          - task: PublishPipelineArtifact@1<br>            displayName: &#39;Publish bundle folder&#39;<br>            inputs:<br>              targetPath: &#39;$(Build.SourcesDirectory)/deployment/native/bundle&#39;<br>              artifactName: &#39;ReactNativeBundles&#39;<br>              artifactType: &#39;pipeline&#39;</pre><h4>2. Building the Android Package (AAB)</h4><p>Using the bundles created previously, we now prepare the Android app:</p><p>We begin by cloning the Mendix native template, integrating the previously generated bundle. Configuring the runtime URL, along with copying necessary assets and configuring the app.</p><p>After installing required dependencies, we use Gradle to create the Android App Bundle. We securely handle the signing process using keystore credentials, verify the signed bundle, and automatically upload it to the Google Play Console. The signed app bundle is saved as a pipeline artifact for easy future reference.</p><p><strong>Steps summary:</strong></p><ul><li>Download bundles from Stage 1</li><li>Install Node.js</li><li>Clone Mendix native template</li><li>Copy Android bundle to the native template</li><li>Set runtime URL</li><li>Copy Mendix native assets</li><li>Copy and configure config.json file</li><li>Install required NPM dependencies</li><li>Apply Mendix native configuration</li><li>Build the Android App Bundle using Gradle</li><li>Download and use secure keystore for signing</li><li>Sign and verify the Android App Bundle</li><li>Upload signed bundle to Google Play Console</li><li>Publish signed bundle as a pipeline artifact</li></ul><pre># This is the stage where we build the Android package<br>- stage: build_android<br>  displayName: &quot;Build Android package on Ubuntu&quot;<br>  dependsOn: build_bundles<br>  jobs:<br>    - job: BuildAndroid<br>      displayName: &quot;Build Android App&quot;<br>      pool:<br>        vmImage: &quot;ubuntu-latest&quot;<br><br>      steps:<br>        # Download the bundles from the previous stage<br>        - task: DownloadPipelineArtifact@2<br>          displayName: &#39;Download bundles from Stage: build_bundles&#39;<br>          inputs:<br>            artifactName: &#39;ReactNativeBundles&#39;<br>            targetPath: &#39;$(Build.SourcesDirectory)/bundles&#39;<br><br>        # Install Node 22.x LTS version<br>        - task: NodeTool@0<br>          displayName: &#39;Install Node 22.x&#39;<br>          inputs:<br>            versionSpec: &#39;22.x&#39;<br>            checkLatest: true<br><br>        # Clone the Mendix Native Template<br>        - task: CmdLine@2<br>          displayName: &#39;Clone GitHub Mendix Native Template (release/${{ variables.nativeTemplateVersion }})&#39;<br>          inputs:<br>            script: |<br>              git clone --single-branch --branch release/$(nativeTemplateVersion) https://github.com/mendix/native-template.git &quot;$(Build.SourcesDirectory)/native-template&quot;<br><br>        # Copy the Android bundle from the downloaded artifact to the native template folder for android<br>        # As outlined here https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally-manually/#bundling-your-mendix-app<br>        - task: CopyFiles@2<br>          displayName: &#39;Copy Android bundle to android/app/src/main&#39;<br>          inputs:<br>            SourceFolder: &#39;$(Build.SourcesDirectory)/bundles/android&#39;<br>            Contents: &#39;**&#39;<br>            TargetFolder: &#39;$(Build.SourcesDirectory)/native-template/android/app/src/main&#39;<br>            OverWrite: true<br><br>        # Set runtime_url in Android<br>        # This is the URL of the Mendix Runtime and set as an secret variable in the pipeline<br>        # See https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&amp;tabs=yaml%2Cbatch#secret-variables<br>        - task: Bash@3<br>          displayName: &#39;Set runtime_url in Android&#39;<br>          inputs:<br>            targetType: inline<br>            script: |<br>              echo &quot;Updating runtime_url with $(runtime-url)&quot;<br>              sed -i &#39;s|^https://.*|$(runtime-url)|&#39; &quot;$(Build.SourcesDirectory)/native-template/android/app/src/main/res/raw/runtime_url&quot;<br><br>        # Copy Mendix Native Assets to the native template folder<br>        # See https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-template/#assets<br>        # I genereated the assets using the Mendix Native Mobile Builder<br>        # Include all files/folders<br>        # Exclude the .config file<br>        - task: CopyFiles@2<br>          displayName: &#39;Copy Mendix Native Assest to the native template folder&#39;<br>          inputs:<br>            SourceFolder: &#39;$(Build.SourcesDirectory)/nativemobile&#39;<br>            Contents: |<br>              **<br>              !.config<br>            TargetFolder: &#39;$(Build.SourcesDirectory)/native-template&#39;<br>            OverWrite: true<br><br>        # Copy the config.json to the native template folder<br>        # for creating this file you can follow the steps outlined here https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-template/#native-mobile-toolkit<br>        # or you can copy it from the Mendix Native Mobile Builder Config output .config file<br>        - task: CopyFiles@2<br>          displayName: &#39;Copy config.json to native template&#39;<br>          inputs:<br>            SourceFolder: &#39;$(Build.SourcesDirectory)/resources&#39;<br>            Contents: &#39;config.json&#39;<br>            TargetFolder: &#39;$(Build.SourcesDirectory)/native-template&#39;<br>            OverWrite: true<br><br>        # Substitute the variables in the config.json<br>        # buildNumber in the config file will be replaced with the versionCode<br>        - task: FileTransform@2<br>          displayName: &#39;Substitute variables in config.json&#39;<br>          inputs:<br>            folderPath: &quot;$(Build.SourcesDirectory)&quot;<br>            jsonTargetFiles: &quot;native-template/config.json&quot;<br>            enableXmlTransform: false<br>            xmlTransformationRules:<br><br>        # Install the required NPM dependencies<br>        - task: Npm@1<br>          displayName: &#39;Install the required NPM dependencies&#39;<br>          inputs:<br>            command: &#39;custom&#39;<br>            customCommand: &#39;install --legacy-peer-deps&#39;<br>            workingDir: &#39;$(Build.SourcesDirectory)/native-template&#39;<br><br>        # Apply the configuration from the Mendix Native Config to the app<br>        - task: Npm@1<br>          displayName: &#39;Apply the configuration from the Mendix Native Config to the app&#39;<br>          inputs:<br>            command: &#39;custom&#39;<br>            customCommand: &#39;run configure&#39;<br>            workingDir: &#39;$(Build.SourcesDirectory)/native-template&#39;<br><br>        # Build the Android App Bundle file<br>        - task: Gradle@3<br>          displayName: &#39;Build Android App Bundle file&#39;<br>          inputs:<br>            gradleWrapperFile: &#39;$(Build.SourcesDirectory)/native-template/android/gradlew&#39;<br>            workingDirectory: &#39;$(Build.SourcesDirectory)/native-template/android/&#39;<br>            tasks: &#39;bundleAppstoreRelease&#39;<br>            publishJUnitResults: false<br>            javaHomeOption: &#39;Path&#39;<br>            jdkDirectory: &#39;$(JAVA_HOME_21_X64)&#39;<br>            gradleOptions: &#39;-Xmx3072m&#39;<br><br>        # To sign the AAB we need to download the keystore from the secure files<br>        # See https://docs.microsoft.com/en-us/azure/devops/pipelines/library/secure-files?view=azure-devops&amp;tabs=yaml<br>        # See https://developer.android.com/studio/publish/app-signing for creating a keystore<br>        - task: DownloadSecureFile@1<br>          displayName: &#39;Download keystore from secure files&#39;<br>          inputs:<br>            secureFile: &#39;mobile-keystore.jks&#39;<br><br>        # Sign the AAB with jarsigner<br>        - task: Bash@3<br>          displayName: &#39;Sign AAB with jarsigner&#39;<br>          inputs:<br>            targetType: inline<br>            script: |<br>              echo &quot;Signing the .aab...&quot;<br><br>              # Path to the downloaded keystore in the agent&#39;s temp folder<br>              KEYS_PATH=&quot;$(Agent.TempDirectory)/mobile-keystore.jks&quot;<br><br>              # Path to your .aab file (adjust as needed)<br>              AAB_PATH=&quot;$(Build.SourcesDirectory)/native-template/android/app/build/outputs/bundle/appstoreRelease/app-appstore-release.aab&quot;<br><br>              # Path for the signed AAB (notice the &#39;-signed&#39; suffix in the filename)<br>              SIGNED_AAB_PATH=&quot;$(Build.SourcesDirectory)/native-template/android/app/build/outputs/bundle/appstoreRelease/app-appstore-release-signed.aab&quot;<br><br>              # Sign the .aab<br>              jarsigner \<br>                -verbose \<br>                -sigalg SHA256withRSA \<br>                -digestalg SHA-256 \<br>                -keystore &quot;$KEYS_PATH&quot; \<br>                -storepass &quot;$(sign-keystore-password)&quot; \<br>                -keypass &quot;$(sign-key-password)&quot; \<br>                -signedjar &quot;$SIGNED_AAB_PATH&quot; \<br>                &quot;$AAB_PATH&quot; \<br>                &quot;$(sign-keystore-alias)&quot;<br><br>              echo &quot;Done signing! Signed file -&gt; $SIGNED_AAB_PATH&quot;<br><br>        # Verify the AAB signature<br>        - task: Bash@3<br>          displayName: &#39;Verify AAB Signature&#39;<br>          inputs:<br>            targetType: inline<br>            script: |<br>              jarsigner -verify -verbose -certs &quot;$(Build.SourcesDirectory)/native-template/android/app/build/outputs/bundle/appstoreRelease/app-appstore-release-signed.aab&quot;<br><br>        # Release the AAB to the Google Play Store<br>        # For this, you need to have a service connection to the Google Play Store<br>        # See https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&amp;tabs=yaml<br>        # See https://marketplace.visualstudio.com/items?itemName=ms-vsclient.google-play<br>        - task: GooglePlayRelease@4<br>          displayName: &#39;Release AAB&#39;<br>          inputs:<br>            serviceEndpoint: &#39;Google Play&#39;<br>            applicationId: &#39;com.mxexperts.mobile&#39;<br>            action: &#39;SingleBundle&#39;<br>            bundleFile: &#39;$(Build.SourcesDirectory)/native-template/android/app/build/outputs/bundle/appstoreRelease/app-appstore-release-signed.aab&#39;<br>            isDraftRelease: true<br>            track: &#39;internal&#39;<br><br>        # Publish the AAB to pipeline artifacts<br>        - task: PublishPipelineArtifact@1<br>          displayName: &#39;Publish AAB to pipeline artifacts&#39;<br>          inputs:<br>            targetPath: &#39;$(Build.SourcesDirectory)/native-template/android/app/build/outputs/bundle/appstoreRelease&#39;<br>            ArtifactName: &#39;signedAab&#39;<br>            artifactType: &quot;pipeline&quot;</pre><h4>3. Building the iOS Package (IPA)</h4><p>At the same time, the iOS package is built:</p><p>We clone the Mendix native template and incorporate the bundles from Stage 1. After configuring the runtime URL and copying necessary assets and configuration files, we handle Apple’s certificate and provisioning requirements.</p><p>The build and signing process is done through Xcode. We manually sign and export the app to an IPA file, then automatically upload it to App Store Connect via TestFlight. Finally, the signed IPA is stored as a pipeline artifact.</p><p><strong>Steps summary:</strong></p><ul><li>Download bundles from Stage 1</li><li>Install Node.js</li><li>Clone Mendix native template</li><li>Copy iOS bundle to the native template</li><li>Set runtime URL</li><li>Copy Mendix native assets</li><li>Copy and configure config.json file</li><li>Install required NPM dependencies</li><li>Apply Mendix native configuration</li><li>Install CocoaPods dependencies</li><li>Securely manage and install Apple certificate and provisioning profile</li><li>Archive and export IPA using Xcode with manual signing</li><li>Upload IPA to App Store Connect (TestFlight)</li><li>Publish signed IPA as a pipeline artifact</li></ul><pre># This is the stage where we build the iOS package<br>- stage: build_ios<br>  displayName: &quot;Build iOS package on macOS&quot;<br>  dependsOn: build_bundles<br>  jobs:<br>    - job: BuildiOS<br>      displayName: &quot;Build iOS App&quot;<br>      pool:<br>        vmImage: &#39;macOS-15&#39;<br><br>      steps:<br>        # Download the bundles from the previous stage<br>        - task: DownloadPipelineArtifact@2<br>          displayName: &#39;Download bundles from Stage: build_bundles&#39;<br>          inputs:<br>            artifactName: &#39;ReactNativeBundles&#39;<br>            targetPath: &#39;$(Build.SourcesDirectory)/bundles&#39;<br><br>        # Install Node 22.x LTS version<br>        - task: NodeTool@0<br>          displayName: &#39;Install Node 22.x&#39;<br>          inputs:<br>            versionSpec: &#39;22.x&#39;<br>            checkLatest: true<br><br>        # Clone the Mendix Native Template<br>        - task: CmdLine@2<br>          displayName: &#39;Clone GitHub Mendix Native Template (release/${{ variables.nativeTemplateVersion }})&#39;<br>          inputs:<br>            script: |<br>              git clone --single-branch --branch release/$(nativeTemplateVersion) https://github.com/mendix/native-template.git &quot;$(Build.SourcesDirectory)/native-template&quot;<br><br>        # Copy the iOS bundle from the downloaded artifact to the native template folder for iOS<br>        - task: CopyFiles@2<br>          displayName: &#39;Copy iOS bundle to ios/Bundle&#39;<br>          inputs:<br>            SourceFolder: &#39;$(Build.SourcesDirectory)/bundles/iOS&#39;<br>            Contents: &#39;**&#39;<br>            TargetFolder: &#39;$(Build.SourcesDirectory)/native-template/ios/Bundle&#39;<br>            OverWrite: true<br><br>        # Set RUNTIME_URL in iOS<br>        - task: Bash@3<br>          displayName: &#39;Set RUNTIME_URL in iOS&#39;<br>          inputs:<br>            targetType: inline<br>            script: |<br>              echo &quot;Updating RUNTIME_URL in iOS to $(runtime-url)&quot;<br>              sed -i &#39;&#39; &quot;s|^RUNTIME_URL=.*|RUNTIME_URL=$(runtime-url)|&quot; \<br>              &quot;$(Build.SourcesDirectory)/native-template/ios/Config/config.xcconfig&quot;<br><br>        # Copy Mendix Native Assets to the native template folder<br>        - task: CopyFiles@2<br>          displayName: &#39;Copy Mendix Native Assets&#39;<br>          inputs:<br>            SourceFolder: &#39;$(Build.SourcesDirectory)/nativemobile&#39;<br>            Contents: |<br>              **<br>              !.config<br>            TargetFolder: &#39;$(Build.SourcesDirectory)/native-template&#39;<br>            OverWrite: true<br><br>        # Copy the config.json to the native template folder<br>        - task: CopyFiles@2<br>          displayName: &#39;Copy config.json to native template&#39;<br>          inputs:<br>            SourceFolder: &#39;$(Build.SourcesDirectory)/resources&#39;<br>            Contents: &#39;config.json&#39;<br>            TargetFolder: &#39;$(Build.SourcesDirectory)/native-template&#39;<br>            OverWrite: true<br><br>        # Substitute the variables in the config.json<br>        - task: FileTransform@2<br>          displayName: &#39;Substitute variables in config.json&#39;<br>          inputs:<br>            folderPath: &quot;$(Build.SourcesDirectory)&quot;<br>            jsonTargetFiles: &quot;native-template/config.json&quot;<br>            enableXmlTransform: false<br>            xmlTransformationRules:<br><br>        # Install the required NPM dependencies<br>        - task: Npm@1<br>          displayName: &#39;Install required NPM dependencies&#39;<br>          inputs:<br>            command: &#39;custom&#39;<br>            customCommand: &#39;install --legacy-peer-deps&#39;<br>            workingDir: &#39;$(Build.SourcesDirectory)/native-template&#39;<br><br>        # Apply the configuration from the Mendix Native Mobile Builder<br>        - task: Npm@1<br>          displayName: &#39;Apply the configuration from the Mendix Native Mobile Builder&#39;<br>          inputs:<br>            command: &#39;custom&#39;<br>            customCommand: &#39;run configure&#39;<br>            workingDir: &#39;$(Build.SourcesDirectory)/native-template&#39;<br><br>        # Install cocoapods dependencies<br>        - task: CocoaPods@0<br>          displayName: &#39;Install CocoaPods dependencies&#39;<br>          inputs:<br>            workingDirectory: &#39;$(Build.SourcesDirectory)/native-template/ios&#39;<br>            forceRepoUpdate: false<br><br>        # Install Apple Certificate used in the Provisioning Profile<br>        # See https://developer.apple.com/help/account/manage-profiles/create-an-app-store-provisioning-profile/<br>        # the file is stored in the secure files<br>        - task: InstallAppleCertificate@2<br>          displayName: &quot;Install Apple Certificate&quot;<br>          inputs:<br>            certSecureFile: &#39;mobile-ios-distribution.p12&#39;<br>            certPwd: &#39;$(ios-dist-cert-password)&#39;<br><br>        # Install Apple Provisioning Profile<br>        # the file is stored in the secure files<br>        - task: InstallAppleProvisioningProfile@1<br>          displayName: &quot;Install Apple Provisioning Profile&quot;<br>          inputs:<br>            provisioningProfileLocation: &#39;secureFiles&#39;<br>            provProfileSecureFile: &#39;Mobile.mobileprovision&#39;<br><br>        # Create an archive of the iOS App<br>        # For this you need to know the CODE_SIGN_IDENTITY, PROVISIONING_PROFILE_SPECIFIER, and DEVELOPMENT_TEAM<br>        # See https://developer.apple.com/documentation/xcode/build-settings-reference<br>        - task: Bash@3<br>          displayName: &#39;Archive iOS App (Manual Signing)&#39;<br>          inputs:<br>            targetType: inline<br>            script: |<br>              xcodebuild \<br>                -workspace &quot;$(Build.SourcesDirectory)/native-template/ios/NativeTemplate.xcworkspace&quot; \<br>                -scheme &quot;nativeTemplate&quot; \<br>                -configuration &quot;Release&quot; \<br>                -sdk &quot;iphoneos&quot; \<br>                -archivePath &quot;$(Build.SourcesDirectory)/native-template/ios/build/NativeTemplate.xcarchive&quot; \<br>                CODE_SIGN_STYLE=Manual \<br>                CODE_SIGN_IDENTITY=&quot;iPhone Distribution: MX Experts (XXXXXXXXXX)&quot; \<br>                PROVISIONING_PROFILE_SPECIFIER=&quot;Mobile&quot; \<br>                DEVELOPMENT_TEAM=&quot;XXXXXXXXXX&quot; \<br>                archive<br><br>        # To export the archive to an IPA file we need to have an exportOptions.plist file<br>        - task: DownloadSecureFile@1<br>          displayName: &#39;Download exportOptions.plist from secure files&#39;<br>          inputs:<br>            secureFile: &#39;exportOptions.plist&#39;<br><br>        # Export the archive to an IPA file<br>        # for this you need to have an exportOptions.plist file<br>        # See https://developer.apple.com/library/archive/technotes/tn2339/_index.html<br>        - task: Bash@3<br>          displayName: &#39;Export iOS IPA&#39;<br>          inputs:<br>            targetType: inline<br>            script: |<br>              xcodebuild \<br>                -exportArchive \<br>                -archivePath &quot;$(Build.SourcesDirectory)/native-template/ios/build/NativeTemplate.xcarchive&quot; \<br>                -exportPath &quot;$(Build.SourcesDirectory)/native-template/ios/build/output&quot; \<br>                -exportOptionsPlist &quot;$(Agent.TempDirectory)/exportOptions.plist&quot;<br><br>        # Publish the IPA to the App Store TestFlight track<br>        # For this, you need to have a service connection to the Apple App Store<br>        # See https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&amp;tabs=yaml<br>        # See https://marketplace.visualstudio.com/items?itemName=ms-vsclient.app-store<br>        - task: AppStoreRelease@1<br>          displayName: &#39;Publish to the App Store TestFlight track&#39;<br>          inputs:<br>            serviceEndpoint: &#39;Apple App Store&#39;<br>            appIdentifier: com.mxexperts.mobile<br>            ipaPath: &#39;$(Build.SourcesDirectory)/native-template/ios/build/output/Mobile.ipa&#39;<br>            shouldSkipWaitingForProcessing: true<br>            shouldSkipSubmission: true<br><br>        # Publish the IPA to pipeline artifacts<br>        - task: PublishPipelineArtifact@1<br>          displayName: &#39;Publish iOS signed IPA to pipeline artifacts&#39;<br>          inputs:<br>            targetPath: &#39;$(Build.SourcesDirectory)/native-template/ios/build/output/Mobile.ipa&#39;<br>            artifactName: &#39;signedIpa&#39;<br>            artifactType: &#39;pipeline&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*LGq_YlFSTcr5GZorjnIAUw.png" /><figcaption>Both packages successfully build</figcaption></figure><h3>Conclusion</h3><p>Implementing this Azure DevOps pipeline greatly improved my Mendix mobile projects. I can now automatically build packages and directly upload them to Google Play and App Store Connect, saving significant time and reducing manual errors. Automated builds enhance reliability, increase productivity, and streamline deployments.</p><h3>Resources</h3><ul><li><a href="https://gist.github.com/tanerg/ea5fbcccfeeb01953e5ed4919c6be20c">Complete Pipeline Script (Gist)</a></li><li><a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally-manually/">Build a Mendix Native App Locally Manually</a></li><li><a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops">Azure DevOps pipeline documentation</a></li></ul><h3>Have Questions?</h3><p><em>If you have any questions or need further clarification on any points discussed in this post, feel free to reach out! I’m always here to help and would love to hear your thoughts. Drop a comment below, and I’ll get back to you as soon as possible. You can also connect with and follow me on </em><a href="https://www.linkedin.com/in/tanergedikoglu/"><em>LinkedIn</em></a><em> for more updates and discussions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=601046ef2913" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mx-experts/app-center-ends-support-heres-your-azure-devops-pipeline-for-mendix-native-app-deployment-601046ef2913">App Center Ends Support — Here’s Your Azure DevOps Pipeline for Mendix Native App Deployment</a> was originally published in <a href="https://medium.com/mx-experts">MX Experts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Show a Loading Indicator on the Splash Screen in a Mendix Native Mobile App]]></title>
            <link>https://medium.com/mx-experts/how-to-show-a-loading-indicator-on-the-splash-screen-in-a-mendix-native-mobile-app-750a20a879e9?source=rss-7955f5494423------2</link>
            <guid isPermaLink="false">https://medium.com/p/750a20a879e9</guid>
            <category><![CDATA[splash-screen]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Taner Gedikoğlu]]></dc:creator>
            <pubDate>Mon, 03 Jun 2024 11:20:13 GMT</pubDate>
            <atom:updated>2024-06-03T11:20:13.878Z</atom:updated>
            <content:encoded><![CDATA[<p>In Mendix native mobile apps, enhancing user experience is crucial. The Mendix splash screen is a static image; during this screen, Mendix is loading resources, performing initial startup tasks, checking for OTA updates, or synchronizing the offline database. One way to improve this is by adding a loading indicator to the splash screen. This informs users that the app is loading and not frozen. In this blog post, we’ll go through the steps to implement a loading indicator on the Mendix splash screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*kbabKhwhvdXT7gLOqdogbw.png" /></figure><h3>Prerequisites</h3><ul><li>Experience in building Mendix native applications.</li><li>Follow the instructions for building a Mendix native app locally as detailed in the <a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/">Mendix documentation</a>.</li><li>Android Studio and Xcode installed on your development machine.</li></ul><h3>Step 1: Create your Custom Build</h3><p>To create a custom build for local development, utilize the Mendix Native Mobile App tool. For comprehensive instructions, refer to the ‘Build a Mendix Native App Locally’ section in the <a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/">Mendix Documentation</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CqnRTJrHmgooSI5nA3NU4g.png" /><figcaption>Mendix Native Mobile App tool</figcaption></figure><p>Choose a directory to save your app’s source code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crn9GZCPO-ErB2rkWvVcJw.png" /><figcaption>Select a directory to save the source code</figcaption></figure><p>Wait for your app to be built:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BfkcMfwPReDBvVDpgiChew.png" /><figcaption>Build your app</figcaption></figure><h3>Step 2: Customize the Splash Screen in Android Studio</h3><p>To be able to open your project in Android Studio, follow the instructions provided in the <a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/#41-building-an-android-app-with-android-studio">Mendix documentation</a> for building a native Android app locally.</p><p>Open the file named <strong>launch_screen.xml</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*ht6DfNoBRQ_qzFlcqndPsw.png" /><figcaption>launch_screen.xml</figcaption></figure><p>Insert the following code beneath the <strong>&lt;ImageView … /&gt;</strong> element:</p><pre>&lt;ProgressBar<br>    android:id=&quot;@+id/progressBar&quot;<br>    android:layout_width=&quot;wrap_content&quot;<br>    android:layout_height=&quot;wrap_content&quot;<br>    android:layout_centerHorizontal=&quot;true&quot;<br>    android:layout_centerVertical=&quot;true&quot;<br>    android:indeterminate=&quot;true&quot;<br>    android:indeterminateTint=&quot;#6D3485&quot; /&gt;</pre><p>The final <strong>launch_screen.xml</strong> file should look something like this:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;<br>&lt;RelativeLayout xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;<br>    android:orientation=&quot;vertical&quot; android:layout_width=&quot;match_parent&quot;<br>    android:layout_height=&quot;match_parent&quot;&gt;<br>    &lt;ImageView android:layout_width=&quot;match_parent&quot; android:layout_height=&quot;match_parent&quot; android:src=&quot;@drawable/splash&quot; android:scaleType=&quot;centerCrop&quot; /&gt;<br>    &lt;!-- Progress Bar --&gt;<br>    &lt;ProgressBar<br>        android:id=&quot;@+id/progressBar&quot;<br>        android:layout_width=&quot;wrap_content&quot;<br>        android:layout_height=&quot;wrap_content&quot;<br>        android:layout_centerHorizontal=&quot;true&quot;<br>        android:layout_centerVertical=&quot;true&quot;<br>        android:indeterminate=&quot;true&quot;<br>        android:indeterminateTint=&quot;#6D3485&quot; /&gt;<br>&lt;/RelativeLayout&gt;</pre><p>The color of the progress bar can be modified by altering the value of the <strong>‘indeterminateTint’</strong> attribute.</p><p>Execute your application now, and a spinning loading indicator should appear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*lkbq_h9XBIisV_EmkW4RLg.gif" /><figcaption>Splash screen with spinning loading indicator</figcaption></figure><h3>Step 3: Customize the Splash Screen in Xcode</h3><p>Normally, iOS does not permit animation on the Launcher screen; however, Mendix’s use of the react-native-splash-screen package enables the display of an activity indicator.</p><p>To open the project in XCode, follow the instructions provided in the <a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/#42-building-an-ios-app-with-xcode">Mendix documentation</a> for building a native iOS app locally.</p><p>Open the <strong>LaunchScreen </strong>storyboard file:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*hJvngYTfDhKLZ5mk3B-C2w.png" /></figure><p>Insert the following code beneath the <strong>&lt;</strong>imageView<strong>… /&gt;</strong> element:</p><pre>&lt;activityIndicatorView style=&quot;large&quot; animating=&quot;YES&quot; hidesWhenStopped=&quot;YES&quot; translatesAutoresizingMaskIntoConstraints=&quot;NO&quot; id=&quot;indicator&quot;&gt;<br> &lt;rect key=&quot;frame&quot; x=&quot;207&quot; y=&quot;448&quot; width=&quot;20&quot; height=&quot;20&quot;/&gt;<br> &lt;color key=&quot;color&quot; white=&quot;1&quot; alpha=&quot;1&quot; colorSpace=&quot;calibratedWhite&quot;/&gt;<br>&lt;/activityIndicatorView&gt;</pre><p>The final <strong>LaunchScreen </strong>storyboard file should look something like this:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;document type=&quot;com.apple.InterfaceBuilder3.CocoaTouch.Storyboard.XIB&quot; version=&quot;3.0&quot; toolsVersion=&quot;16096&quot; targetRuntime=&quot;iOS.CocoaTouch&quot; propertyAccessControl=&quot;none&quot; useAutolayout=&quot;YES&quot; launchScreen=&quot;YES&quot; useTraitCollections=&quot;YES&quot; useSafeAreas=&quot;YES&quot; colorMatched=&quot;YES&quot; initialViewController=&quot;01J-lp-oVM&quot;&gt;<br> &lt;device id=&quot;retina6_1&quot; orientation=&quot;portrait&quot; appearance=&quot;light&quot;/&gt;<br> &lt;dependencies&gt;<br>  &lt;deployment identifier=&quot;iOS&quot;/&gt;<br>  &lt;plugIn identifier=&quot;com.apple.InterfaceBuilder.IBCocoaTouchPlugin&quot; version=&quot;16087&quot;/&gt;<br>  &lt;capability name=&quot;Safe area layout guides&quot; minToolsVersion=&quot;9.0&quot;/&gt;<br>  &lt;capability name=&quot;documents saved in the Xcode 8 format&quot; minToolsVersion=&quot;8.0&quot;/&gt;<br> &lt;/dependencies&gt;<br> &lt;scenes&gt;<br>  &lt;!--View Controller--&gt;<br>  &lt;scene sceneID=&quot;EHf-IW-A2E&quot;&gt;<br>   &lt;objects&gt;<br>    &lt;viewController id=&quot;01J-lp-oVM&quot; sceneMemberID=&quot;viewController&quot;&gt;<br>     &lt;view key=&quot;view&quot; contentMode=&quot;scaleToFill&quot; id=&quot;Ze5-6b-2t3&quot;&gt;<br>      &lt;rect key=&quot;frame&quot; x=&quot;0.0&quot; y=&quot;0.0&quot; width=&quot;414&quot; height=&quot;896&quot;/&gt;<br>      &lt;autoresizingMask key=&quot;autoresizingMask&quot; widthSizable=&quot;YES&quot; heightSizable=&quot;YES&quot;/&gt;<br>      &lt;subviews&gt;<br>       &lt;imageView clipsSubviews=&quot;YES&quot; userInteractionEnabled=&quot;NO&quot; contentMode=&quot;scaleAspectFill&quot; horizontalHuggingPriority=&quot;251&quot; verticalHuggingPriority=&quot;251&quot; fixedFrame=&quot;YES&quot; image=&quot;SplashScreen&quot; translatesAutoresizingMaskIntoConstraints=&quot;NO&quot; id=&quot;zaa-Dw-Efy&quot;&gt;<br>        &lt;rect key=&quot;frame&quot; x=&quot;0.0&quot; y=&quot;0.0&quot; width=&quot;414&quot; height=&quot;896&quot;/&gt;<br>        &lt;autoresizingMask key=&quot;autoresizingMask&quot; widthSizable=&quot;YES&quot; heightSizable=&quot;YES&quot;/&gt;<br>       &lt;/imageView&gt;<br>       &lt;activityIndicatorView style=&quot;large&quot; animating=&quot;YES&quot; hidesWhenStopped=&quot;YES&quot; translatesAutoresizingMaskIntoConstraints=&quot;NO&quot; id=&quot;indicator&quot;&gt;<br>        &lt;rect key=&quot;frame&quot; x=&quot;207&quot; y=&quot;448&quot; width=&quot;20&quot; height=&quot;20&quot;/&gt;<br>        &lt;color key=&quot;color&quot; white=&quot;1&quot; alpha=&quot;1&quot; colorSpace=&quot;calibratedWhite&quot;/&gt;<br>       &lt;/activityIndicatorView&gt;<br>      &lt;/subviews&gt;<br>      &lt;color key=&quot;backgroundColor&quot; red=&quot;1&quot; green=&quot;1&quot; blue=&quot;1&quot; alpha=&quot;1&quot; colorSpace=&quot;custom&quot; customColorSpace=&quot;sRGB&quot;/&gt;<br>      &lt;viewLayoutGuide key=&quot;safeArea&quot; id=&quot;Bcu-3y-fUS&quot;/&gt;<br>     &lt;/view&gt;<br>    &lt;/viewController&gt;<br>    &lt;placeholder placeholderIdentifier=&quot;IBFirstResponder&quot; id=&quot;iYj-Kq-Ea1&quot; userLabel=&quot;First Responder&quot; sceneMemberID=&quot;firstResponder&quot;/&gt;<br>   &lt;/objects&gt;<br>   &lt;point key=&quot;canvasLocation&quot; x=&quot;52.173913043478265&quot; y=&quot;375&quot;/&gt;<br>  &lt;/scene&gt;<br> &lt;/scenes&gt;<br> &lt;resources&gt;<br>  &lt;image name=&quot;SplashScreen&quot; width=&quot;80.5&quot; height=&quot;157&quot;/&gt;<br> &lt;/resources&gt;<br>&lt;/document&gt;</pre><p>Execute your application now, and a spinning loading indicator should appear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*syOronMwvaNbBQG365hSYQ.gif" /></figure><h3>Conclusion</h3><p>By following these steps, you’ve successfully added a loading indicator to the Mendix splash screen in your native mobile app. This enhancement provides visual feedback during the app’s loading process, OTA updates, and offline database synchronization, significantly improving user experience. Customize the loading indicator and splash screen to match your app’s branding and design.</p><h3><em>Have Questions?</em></h3><p><em>If you have any questions or need further clarification on any points discussed in this post, feel free to reach out! I’m always here to help and would love to hear your thoughts. Drop a comment below, and I’ll get back to you as soon as possible. You can also connect with and follow me on </em><a href="https://www.linkedin.com/in/tanergedikoglu/"><em>LinkedIn</em></a><em> for more updates and discussions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=750a20a879e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mx-experts/how-to-show-a-loading-indicator-on-the-splash-screen-in-a-mendix-native-mobile-app-750a20a879e9">How to Show a Loading Indicator on the Splash Screen in a Mendix Native Mobile App</a> was originally published in <a href="https://medium.com/mx-experts">MX Experts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>