<?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 Bas Jonker on Medium]]></title>
        <description><![CDATA[Stories by Bas Jonker on Medium]]></description>
        <link>https://medium.com/@bas.jonker?source=rss-6930de539b77------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bsJNwrdJhKNYSRwo4cgYGg.jpeg</url>
            <title>Stories by Bas Jonker on Medium</title>
            <link>https://medium.com/@bas.jonker?source=rss-6930de539b77------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:54:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bas.jonker/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[Mendix Native builds with Azure Pipelines]]></title>
            <link>https://medium.com/mendix/mendix-native-builds-with-azure-pipelines-d421c0c67ff7?source=rss-6930de539b77------2</link>
            <guid isPermaLink="false">https://medium.com/p/d421c0c67ff7</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[azure-pipelines]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[native-app]]></category>
            <dc:creator><![CDATA[Bas Jonker]]></dc:creator>
            <pubDate>Wed, 26 Mar 2025 12:07:34 GMT</pubDate>
            <atom:updated>2025-06-03T13:51:25.670Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UMrSS1ufq6yl0b88crDO_A.png" /></figure><h4>With the retirement of Microsoft AppCenter, Mendix developers had to find an alternative way to build their Native apps. Another option is to use <a href="https://azure.microsoft.com/en-us/products/devops/pipelines">Azure Pipelines</a>!</h4><h4>This is a CI/CD tool within Azure DevOps that automates the process of building, testing, and deploying.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7UCljL-xYpLtT0HQhjf_Jw.png" /></figure><p>There are many build tools available on the market. Mendix has already published <a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/building-native-apps/bitrise/">documentation</a> for implementing the CI/CD tool <a href="https://bitrise.io/">Bitrise</a>. This guide outlines the basic process to use Azure Pipelines as an alternative to Bitrise.</p><blockquote>Note : This blog provides a basic example with the aim of being able to download the build package (.apk or .ipa). The pipeline can be configured in many ways.</blockquote><p>Below are the steps for Azure Pipelines. I have already configured the Mendix Native Mobile Builder and pushed it to my GitHub repository.</p><p>If you see any improvements, please let me know :)</p><h4><strong>Set up the pipeline</strong></h4><ol><li><a href="https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/create-organization?view=azure-devops">Create an organization</a></li><li><a href="https://learn.microsoft.com/en-us/azure/devops/organizations/projects/create-project?view=azure-devops">Create a project</a> within the organization</li><li><a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/create-first-pipeline?view=azure-devops">Create a pipeline</a> within your project. I created separate pipelines for Android and iOS. At the ‘Configure’ step, select the Android- or XCode template depending on your goal. For the correct YAML configuration, check out the next sections of this blog</li></ol><h4><strong>Upload signing documents</strong></h4><p>The pipeline needs certain files to sign a build. For Android, a keystore is required, and for iOS, a distribution certificate and provisioning profile are needed. These files can be uploaded in the ‘<a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/library/secure-files?view=azure-devops">Secure files</a>’ tab within the ‘Library’ section.</p><blockquote><strong>Note</strong> : You need to give your files the right permissions for your pipeline(s) to access these files.</blockquote><h3>Android and iOS</h3><p><strong>Set Node version (optional)</strong></p><p>The Azure Pipeline build agent uses a default Node version. You may need a specific version (especially for older Native Template versions).</p><p>You can deduce which Node versions you can use from the package.json of your Native Template:</p><pre>  &quot;engines&quot;: {<br>    &quot;node&quot;: &quot;&gt;=18&quot;<br>  },</pre><p>If you need a specific version, you can use the <a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/use-node-v1?view=azure-pipelines">‘UseNode’ task</a> to use a specific version:</p><pre>- task: UseNode@1<br>  inputs:<br>    version: &#39;18.x&#39;</pre><p><strong>Install required dependencies</strong></p><ol><li>Select the task ‘npm’</li><li>Select ‘Install’ at ‘Command’</li><li>Click on ‘Add’</li></ol><pre>- task: Npm@1<br>  inputs:<br>    command: &#39;install&#39;</pre><p><strong>Apply the Mendix Native Mobile Builder configuration</strong></p><ol><li>Select the task ‘npm’</li><li>Select ‘custom’ from the dropdown</li><li>Fill this in at ‘Command and arguments’: run configure</li><li>Click on ‘Add’</li></ol><pre>- task: Npm@1<br>  inputs:<br>    command: &#39;custom&#39;<br>    customCommand: &#39;run configure&#39;</pre><h3><strong>Android</strong></h3><p><strong>Build</strong></p><ol><li>Select the task ‘Gradle’</li><li>Fill this in at ‘Gradle wrapper’: android/gradlew</li><li>Fill this in at ‘Working directory’: android</li><li>Fill this in at ‘Tasks’: assembleRelease</li><li>Uncheck the JUnit option ‘Publish to Azure Pipelines’</li><li>To avoid <a href="https://docs.gradle.org/current/userguide/compatibility.html">incompatibility</a> between Java and Gradle versions, set the ‘JDK version’ based on which Gradle version your Native Template uses (see ‘./android/gradle/wrapper/gradle-wrapper.properties)’. At the time of writing, ‘JDK 17’ works for MX 10.18.x and 9.24.x applications.</li><li>Click on ‘Add’</li></ol><pre>- task: Gradle@4<br>  inputs:<br>    gradleWrapperFile: &#39;android/gradlew&#39;<br>    workingDirectory: &#39;android&#39;<br>    tasks: &#39;assembleRelease&#39;<br>    publishJUnitResults: false<br>    javaHomeOption: &#39;JDKVersion&#39;<br>    jdkVersionOption: &#39;1.17&#39;<br>    sonarQubeRunAnalysis: false<br>    spotBugsAnalysis: false</pre><p><strong>Sign build</strong></p><ol><li>Select the task ‘Android signing’</li><li>Fill in your keystore file name at ‘Keystore file’ (for example ‘mykeystore.keystore’). This must be the same name as in the Secure Files.</li><li>Fill in the keystore password, alias, and key password</li><li>Click on ‘Add’</li></ol><pre>- task: AndroidSigning@3<br>  inputs:<br>    apkFiles: &#39;**/*.apk&#39;<br>    apksignerKeystoreFile: &#39;$(KeystoreName)&#39;<br>    apksignerKeystorePassword: &#39;$(KeystorePassword)&#39;<br>    apksignerKeystoreAlias: &#39;$(KeyAlias)&#39;<br>    apksignerKeyPassword: &#39;$(KeyPassword)&#39;</pre><p><strong>Copy and publish the build artifact</strong></p><p>This step will make the build downloadable in your pipeline afterwards. There are also other options to publish your build to another location</p><ol><li>Select the task ‘Copy files’</li><li>Fill this in at ‘Contents’: **/*.apk</li><li>Fill this in at ‘Target Folder’: $(Build.ArtifactStagingDirectory)<br>This is an <a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&amp;tabs=yaml#build-variables-devops-services">Azure build variable</a>. You don’t have to define this by yourself</li><li>Click on ‘Add’</li></ol><pre>- task: CopyFiles@2<br>  inputs:<br>    Contents: &#39;**/*.apk&#39;<br>    TargetFolder: &#39;$(Build.ArtifactStagingDirectory)&#39;</pre><ol><li>Select the task ‘Publish build artifacts’</li><li>Change the ‘Artifact name’ to your liking</li><li>Click on ‘Add’</li></ol><pre>- task: PublishBuildArtifacts@1<br>  inputs:<br>    PathtoPublish: &#39;$(Build.ArtifactStagingDirectory)&#39;<br>    ArtifactName: &#39;drop&#39;<br>    publishLocation: &#39;Container&#39;</pre><p><strong>Android final result</strong></p><pre># Android<br># Build your Android project with Gradle.<br># Add steps that test, sign, and distribute the APK, save build artifacts, and more:<br># https://docs.microsoft.com/azure/devops/pipelines/languages/android<br><br>trigger:<br>- master<br><br>pool:<br>  vmImage: &#39;macos-latest&#39;<br><br>steps:<br>- task: Npm@1<br>  inputs:<br>    command: &#39;install&#39;<br>- task: Npm@1<br>  inputs:<br>    command: &#39;custom&#39;<br>    customCommand: &#39;run configure&#39;<br>- task: Gradle@4<br>  inputs:<br>    gradleWrapperFile: &#39;android/gradlew&#39;<br>    workingDirectory: &#39;android&#39;<br>    tasks: &#39;assembleRelease&#39;<br>    publishJUnitResults: false<br>    javaHomeOption: &#39;JDKVersion&#39;<br>    jdkVersionOption: &#39;1.17&#39;<br>    sonarQubeRunAnalysis: false<br>    spotBugsAnalysis: false<br>- task: AndroidSigning@3<br>  inputs:<br>    apkFiles: &#39;**/*.apk&#39;<br>    apksignerKeystoreFile: &#39;$(KeystoreName)&#39;<br>    apksignerKeystorePassword: &#39;$(KeystorePassword)&#39;<br>    apksignerKeystoreAlias: &#39;$(KeyAlias)&#39;<br>    apksignerKeyPassword: &#39;$(KeyPassword)&#39;<br>- task: CopyFiles@2<br>  inputs:<br>    Contents: &#39;**/*.apk&#39;<br>    TargetFolder: &#39;$(Build.ArtifactStagingDirectory)&#39;<br>- task: PublishBuildArtifacts@1<br>  inputs:<br>    PathtoPublish: &#39;$(Build.ArtifactStagingDirectory)&#39;<br>    ArtifactName: &#39;drop&#39;<br>    publishLocation: &#39;Container&#39;</pre><p><strong>Download the build artifact</strong></p><ol><li>Go to the details of the build run</li><li>You can find the build in the ‘Summary’. If you want the signed files to have different names, there are options to rename the files during the build</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ta8orpdOV0MzHmcIBTp1Ag.png" /></figure><h3>iOS</h3><p><strong>Install iOS dependencies</strong></p><ol><li>Select the task ‘CocoaPods’</li><li>Fill this in at ‘Working directory’: ios</li><li>Click on ‘Add’</li></ol><pre>- task: CocoaPods@0<br>  inputs:<br>    workingDirectory: &#39;ios&#39;<br>    forceRepoUpdate: false</pre><p><strong>Install the distribution certificate</strong></p><ol><li>Select the task ‘Install Apple certificate’</li><li>Fill in your certificate name at ‘Certificate (P12)’. For example, ‘MyCertificate.p12’. This must be the same name as in the Secure Files.</li><li>Fill in the ‘Certificate (P12) password’</li><li>Expand the dropdown and declare your ‘Certificate signing identity’ to your liking. You can use this later in the XCode step. If you leave this empty, it will be something like ‘<em>iPhone Distribution: Your Company Name (Team ID)</em>’</li><li>Click on ‘Add’</li></ol><pre>- task: InstallAppleCertificate@2<br>  inputs:<br>    certSecureFile: &#39;$(CertificateName)&#39;<br>    certPwd: &#39;$(P12password)&#39;<br>    keychain: &#39;temp&#39;<br>    signingIdentity: &#39;$(SigningIdentity)&#39;</pre><p><strong>Install the provisioning profile</strong></p><ol><li>Select the task ‘Install Apple provisioning profile’</li><li>Fill in your provisioning profile name at ‘Provisioning profile’. For example, ‘MyProfile.mobileprovision’. This must be the same name as in the Secure Files.</li><li>Click on ‘Add’</li></ol><pre>- task: InstallAppleProvisioningProfile@1<br>  inputs:<br>    provisioningProfileLocation: &#39;secureFiles&#39;<br>    provProfileSecureFile: &#39;$(ProvisioningProfileName)&#39;</pre><p><strong>Build</strong></p><ol><li>Select the task ‘Xcode’</li><li>Fill this in at ‘Actions’: archive</li><li>Fill this in at ‘Configuration’: Release</li><li>Fill this in at ‘Workspace or project path’: ios/NativeTemplate.xcworkspace</li><li>Fill this in at ‘Scheme’: nativeTemplate</li><li>Select ‘Manual signing’ at ‘Signing style’</li><li>At ‘Signing identity’, fill in the signing identity you declared in the ‘Install distribution certificate’ step</li><li>Fill in the provisioning profile UUID at ‘Provisioning profile UUID’. You can find this when opening your provisioning profile in a text editor (e.g., Visual Studio Code). I used the UUID instead of the name so as not to be dependent on what name the agent gives to the profile during the build</li><li>Check the ‘Create app package’ box</li><li>Click on ‘Add’</li></ol><pre>- task: Xcode@5<br>  inputs:<br>    actions: &#39;archive&#39;<br>    configuration: &#39;Release&#39;<br>    sdk: &#39;iphoneos&#39;<br>    xcWorkspacePath: &#39;ios/NativeTemplate.xcworkspace&#39;<br>    scheme: &#39;nativeTemplate&#39;<br>    packageApp: true<br>    signingOption: &#39;manual&#39;<br>    signingIdentity: &#39;$(SigningIdentity)&#39;<br>    provisioningProfileUuid: &#39;$(ProvisioningProfileUUID)&#39;</pre><p><strong>Copy and publish the build artifact</strong></p><p>This step will make the build downloadable in your pipeline afterwards. There are also other options to publish your build to another location</p><ol><li>Select the task ‘Copy files’</li><li>Fill this in at ‘Contents’: **/*.ipa</li><li>Fill this in at ‘Target Folder’: $(Build.ArtifactStagingDirectory)<br>This is an <a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&amp;tabs=yaml#build-variables-devops-services">Azure build variable</a>. You don’t have to define this by yourself</li><li>Click on ‘Add’</li></ol><pre>- task: CopyFiles@2<br>  inputs:<br>    Contents: &#39;**/*.ipa&#39;<br>    TargetFolder: &#39;$(Build.ArtifactStagingDirectory)&#39;</pre><ol><li>Select the task ‘Publish build artifacts’</li><li>Change the ‘Artifact name’ to your liking</li><li>Click on ‘Add’</li></ol><pre>- task: PublishBuildArtifacts@1<br>  inputs:<br>    PathtoPublish: &#39;$(Build.ArtifactStagingDirectory)&#39;<br>    ArtifactName: &#39;drop&#39;<br>    publishLocation: &#39;Container&#39;</pre><p><strong>iOS final result</strong></p><pre># Xcode<br># Build, test, and archive an Xcode workspace on macOS.<br># Add steps that install certificates, test, sign, and distribute an app, save build artifacts, and more:<br># https://docs.microsoft.com/azure/devops/pipelines/languages/xcode<br><br>trigger:<br>- master<br><br>pool:<br>  vmImage: &#39;macos-latest&#39;<br><br>steps:<br>- task: Npm@1<br>  inputs:<br>    command: &#39;install&#39;<br>- task: Npm@1<br>  inputs:<br>    command: &#39;custom&#39;<br>    customCommand: &#39;run configure&#39;<br>- task: CocoaPods@0<br>  inputs:<br>    workingDirectory: &#39;ios&#39;<br>    forceRepoUpdate: false<br>- task: InstallAppleCertificate@2<br>  inputs:<br>    certSecureFile: &#39;$(CertificateName)&#39;<br>    certPwd: &#39;$(P12password)&#39;<br>    keychain: &#39;temp&#39;<br>    signingIdentity: &#39;$(SigningIdentity)&#39;<br>- task: InstallAppleProvisioningProfile@1<br>  inputs:<br>    provisioningProfileLocation: &#39;secureFiles&#39;<br>    provProfileSecureFile: &#39;$(ProvisioningProfileName)&#39;<br>- task: Xcode@5<br>  inputs:<br>    actions: &#39;archive&#39;<br>    configuration: &#39;Release&#39;<br>    sdk: &#39;iphoneos&#39;<br>    xcWorkspacePath: &#39;ios/NativeTemplate.xcworkspace&#39;<br>    scheme: &#39;nativeTemplate&#39;<br>    packageApp: true<br>    signingOption: &#39;manual&#39;<br>    signingIdentity: &#39;$(SigningIdentity)&#39;<br>    provisioningProfileUuid: &#39;$(ProvisioningProfileUUID)&#39;<br>- task: CopyFiles@2<br>  inputs:<br>    Contents: &#39;**/*.ipa&#39;<br>    TargetFolder: &#39;$(Build.ArtifactStagingDirectory)&#39;<br>- task: PublishBuildArtifacts@1<br>  inputs:<br>    PathtoPublish: &#39;$(Build.ArtifactStagingDirectory)&#39;<br>    ArtifactName: &#39;drop&#39;<br>    publishLocation: &#39;Container&#39;</pre><p><strong>Download the build artifact</strong></p><ol><li>Go to the details of the build run</li><li>You can find the build in the ‘Summary’ tab. If you want the signed files to have different names, there are options to rename the files during the build</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ta8orpdOV0MzHmcIBTp1Ag.png" /></figure><p><strong>Known issues</strong></p><p>With some Native templates, signing the iOS build can result in an error like this:<br> ‘<em>error: Provisioning profile “MyProvisioningProfile” belongs to team “MyAppleDeveloperCompany”, which does not match the selected team “BC32QNM6AD”. (in target ‘nativeTemplate’ from project ‘nativeTemplate</em>’)’. See the downloaded log folder ‘<em>Job\12_xcodebuild.log</em>’</p><p>The reason for this is the hardcoded Apple Developer TeamID(‘s) in the native template file ‘ios/nativeTemplate.xcodeproj/project.pbxproj’.</p><p>Until I fixed this, the workaround for this is to delete all the lines with <em>DEVELOPMENT_TEAM (for example ‘</em>’<em>DEVELOPMENT_TEAM = BC32QNM6AD;</em>’) in this file before building.</p><h4>Read more</h4><ul><li><a href="https://docs.mendix.com/refguide/mobile/introduction-to-mobile-technologies/native-mobile/">Native Mobile</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></ul><p><strong><em>From the Publisher -</em></strong></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d421c0c67ff7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/mendix-native-builds-with-azure-pipelines-d421c0c67ff7">Mendix Native builds with Azure Pipelines</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>