<?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 Sabahudin Kodro on Medium]]></title>
        <description><![CDATA[Stories by Sabahudin Kodro on Medium]]></description>
        <link>https://medium.com/@sabahudin.kodro?source=rss-561617ae9d0b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*fS7zlXK2HyBrbFl4bvuS4w.jpeg</url>
            <title>Stories by Sabahudin Kodro on Medium</title>
            <link>https://medium.com/@sabahudin.kodro?source=rss-561617ae9d0b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:36:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sabahudin.kodro/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[A Developer’s Guide to Proper Desk Sitting | RUBICON]]></title>
            <link>https://medium.com/rubicon-stories/a-developers-guide-to-proper-desk-sitting-rubicon-d29a6654da1c?source=rss-561617ae9d0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d29a6654da1c</guid>
            <category><![CDATA[posture]]></category>
            <category><![CDATA[office-furniture]]></category>
            <category><![CDATA[ergonomics]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[Sabahudin Kodro]]></dc:creator>
            <pubDate>Tue, 18 Jun 2019 07:34:55 GMT</pubDate>
            <atom:updated>2019-06-18T13:13:06.641Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tbS1i3CX3kPfKpy6igrMQQ.png" /></figure><p>We spend countless hours hunched over at our desks, typing away and squinting at our screens while working on a code. And naturally, we focus on getting the job done instead of paying attention to our posture and the length of time we spend sitting in the same position.</p><h3>Poor Work Habits Lead to Health Issues</h3><p>You may already have some poor habits outside of the workplace that damage your health such as smoking, not exercising, a poor diet and spending a lot of time sitting. What about your poor habits IN the workplace?</p><p>After all, on average we spend about 40 hours a week working and most of that time is spent sitting. The longer you sit, the worse your posture becomes.</p><p>Some say that sitting is the new smoking. A bad posture and sitting for a long time can lead to many health risks such as back &amp; neck pain, muscle stiffness, an increased risk of cardiovascular disease and a variety of other issues.</p><p>If you catch yourself taking part in any of the following habits, then you’re putting yourself at risk:</p><ul><li>Sitting with knees, ankles or arms crossed.</li><li>Sitting slumped to one side.</li><li>Not properly supporting the feet.</li><li>Not fully supporting the back (especially the lower back).</li><li>Sitting with your spine in a ‘C Shape.’</li><li>Sitting in one position for a long time.</li><li>Straining the neck for long periods of time while staring at a screen.</li><li>Sitting for an extended period of time without taking a break.</li></ul><h3>Correct Sitting Posture</h3><p>There are a few steps you can take in order to ensure healthy habits at work. Firstly, let’s take a look at sitting properly in a comfortable chair, it may sound super simple but most of us don’t follow proper sitting.</p><p>Follow these simple steps in order to sit properly:</p><ul><li>Take a seat in your chair and plant your feet on the floor or on a footrest.</li><li>Push your hips as far back as they can go in the chair.</li><li>Keep your shoulders and back straight and focus on keeping your lower back supported on the back of the chair.</li><li>Leave a small gap between the back of your knees and the chair.</li><li>Position your knees at the same height or slightly lower than your hips and place your ankles in front of your knees.</li><li>Recline the back of the chair to a 100 to 110-degree angle.</li><li>Adjust your armrests so that your shoulders are relaxed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*JyrPTmUyRqEolgQO.jpg" /></figure><p>There you have it, you’re sitting properly in your chair. Now that’s only one part to proper desk sitting. Let’s set up your desk for the ideal work environment.</p><h3>Setting Up Your Workspace for Success</h3><p>Setting up your workplace is as important as sitting properly for your health. Check out how to set up your workspace:</p><p><strong>Setting up your desk:</strong></p><p>Adjust the height of your chair so you are able to roll up to your desk and fit both of your feet and the chair’s armrests comfortably underneath. Adjust your chair so that your arms are bent to 90 degrees.</p><p><strong>Setting up your monitor:</strong></p><p>It is very important to adjust your monitor to the correct height since constantly looking up or down can make you tired and eventually lead to eye strain. Place your monitor in front of you, arms length away and at eye level height since this will ensure that your neck will be straight and relaxed.</p><p><strong>Setting up your mouse &amp; keyboard:</strong></p><p>Place the mouse and keyboard directly in front of you and as central to your body as possible. Position both the mouse and keyboard at about elbow height. If you’re using a keyboard tray, place it just above your thighs for the ideal position.</p><p>If you want to find out the ideal height to adjust your chair, monitor and keyboard, you can <a href="https://www.ergotron.com/tools/workspace-planner">check out this site</a> where you’re able to place your height &amp; it will give you the proper dimensions.</p><h3>A Few Additional Tips to Staying Healthy at Work</h3><p>Here are a few additional tips you can follow to achieve the ideal healthy workday:</p><p><strong>Avoid sitting for long periods of time-</strong> It is recommended that you take stretch breaks every 20 to 30 minutes so you’re not constantly sitting. Get up on your feet, even if you’re standing beside your desk and not moving around it is still better than sitting.</p><p><strong>Give a standing desk a try-</strong> If your desk is adjustable, you are able to work in a standing position just make sure to adjust it properly to your height. Working while standing can be just as effective as sitting!</p><p><strong>Eating healthy &amp; drinking plenty of water-</strong> Don’t let your work completely consume you, remember to keep hydrated and always have healthy food available in your workspace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*pCtcPyyVWEZf8Z1C.jpg" /></figure><h3>RUBICON: An Ergonomic Workplace</h3><p>RUBICON, a software development company located in Sarajevo, Bosnia &amp; Herzegovina practices proper desk sitting and healthy work habits. Our office space is an ideal work environment offering ergonomic materials to help you get comfortable in your desk space.</p><p>Each team member has their own office space that is accompanied by:</p><ul><li>A heigh adjustable standing desk.</li><li>A soft cushioned adjustable chair with lower back support.</li><li>An ergonomic keyboard &amp; monitor.</li><li>Space around the office to walk, stretch and take a break whenever needed.</li></ul><p>Using these appliances, I’m able to create my own workspace in which I feel both comfortable and productive:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*-o7RFESu9Mc-Ban_.jpg" /></figure><h3>Create your own healthy workspace</h3><p>The average person spends around 90,000 hours at work, therefore healthy habits are very important. You too can create your own ideal workspace and be mindful to how you’re sitting at your desk to avoid health issues. I challenge you to make a change in your work environment!</p><p><em>Originally published at </em><a href="https://www.rubicon-world.com/blog/2019/06/a-developers-guide-to-proper-desk-sitting/"><em>https://www.rubicon-world.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d29a6654da1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rubicon-stories/a-developers-guide-to-proper-desk-sitting-rubicon-d29a6654da1c">A Developer’s Guide to Proper Desk Sitting | RUBICON</a> was originally published in <a href="https://medium.com/rubicon-stories">RUBICON Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automated Deployment with Fastlane on iOS | RUBICON]]></title>
            <link>https://medium.com/rubicon-stories/automated-deployment-with-fastlane-on-ios-rubicon-ef9a72898947?source=rss-561617ae9d0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef9a72898947</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[fastlane]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Sabahudin Kodro]]></dc:creator>
            <pubDate>Mon, 20 May 2019 14:19:16 GMT</pubDate>
            <atom:updated>2019-05-21T07:24:51.470Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ErN-TPXui1xlSvrbf4eOLw@2x.jpeg" /></figure><p>As iOS developers, we’ve all experienced the satisfying feeling of finally finishing coding an app and being excited to share it with users. Prior to users enjoying the app, there is only one more thing left to do- release the app to the App Store! Surely, you think it shouldn’t take longer than a few minutes of your time?</p><p>Oh, you’re completely wrong.</p><p>In order to reach that step, the following is needed:</p><ul><li>Ensure you have the right certificates and provisioning profiles in place.</li><li>Create a variety of screenshots of the app.</li><li>Build the app.</li><li>Upload the app to App Store Connect.</li><li>Log in to App Store Connect, input the correct metadata and inspect the upload.</li><li>Submit the app for review and wait.</li></ul><p>These steps are just one approach to deploying your app as there are many more aspects that should be considered, such as dealing with build/version numbers, running tests, uploading beta releases etc.</p><p>Why is this so difficult?</p><p>Well actually, it <em>used</em> to be difficult but thanks to Fastlane, all of the mentioned steps above can be automated. Continue reading this blog to find out how Fastlane can help you!</p><h3>Blog Overview</h3><p>This blog will introduce Fastlane, the advantages it provides and present concrete scenarios showing how it automates the deployment of an application. The following examples of automation will be covered:</p><ul><li>The creation of an app</li><li>Generation of certificates and provisioning profiles</li><li>Deployment to Testflight</li><li>Deployment to App Store</li></ul><p>The focus and examples used in this blog will be for iOS. However, the same principles (and in many cases the same commands) apply for Android as well.</p><p><strong>Important note:</strong> in order to use Fastlane for iOS, you need to have a paid Apple Developer Account.</p><h3>What is Fastlane?</h3><p>Before moving on to how to operate Fastlane, it is important to know what it is and how to set it up properly.</p><p><strong>Fastlane Features</strong></p><p><a href="https://docs.fastlane.tools/">Fastlane</a> is a tool that helps automate the development and release process for mobile apps.</p><p>It’s main features include:</p><ul><li>Automated generation of screenshots</li><li>Beta deployment</li><li>App Store deployment</li><li>Code signing</li></ul><h3>Setting Up Fastlane</h3><p>Follow these steps, taken from Fastlane’s <a href="https://docs.fastlane.tools/#getting-started">official documentation</a>, in order to properly setup Fastlane.</p><p>1. <strong>Install latest Xcode command line tools</strong></p><pre>xcode-select --install</pre><p>2. <strong>Install Fastlane</strong></p><pre># Using Ruby<br>Gems gem install fastlane -NV</pre><pre># Alternatively using Homebrew <br>brew cask install fastlane</pre><p>3. <strong>Navigate to project and run</strong></p><pre>fastlane init</pre><p><strong>Appfile and Fastfile</strong></p><p>After running <strong>fastlane init</strong>, Fastlane automatically creates a new folder within the project called &#39;Fastlane&#39;. This folder contains two files: Appfile and Fastfile which are used to help automate the deployment process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*6RW5dpXjwoJLGDvz.png" /></figure><p><strong>Illustration 1: Fastlane folder structure</strong></p><p>The <strong>Appfile</strong> contains information about the developer and the app, such as the developer Apple email and the app ID of the application. The <strong>Fastfile</strong> contains different lanes, written in Ruby, which represent distinct workflows, or in other words, different automation tasks. We can create and customize these, however we’d like. For example, a lane can automate releases to Testflight or deployments to the App Store. The Fastfile is the file where developers spend the most time when it comes to Fastlane.</p><h3>Using Fastlane</h3><p>Now let’s look at some examples of how to automate tasks using Fastlane.</p><p><strong>Our First Fastfile Lane: App Creation</strong><br>In order to successfully upload a new build to the App Store, we first have to create the app on App Store Connect and on the Apple Developer Portal. Although this process is not too complicated, it is still a bit tedious to complete. Therefore, this is a good starting point for automation with Fastlane.</p><p>First, open the Appfile and input a few parameters:</p><pre>app_identifier ‘[[YOUR APP IDENTIFIER]]’ # The bundle identifier of the app apple_id ‘[[YOUR APPLE EMAIL]]’ # Apple email address team_id ‘[[YOU TEAM ID]]’ # Team ID from the Developer Portal itc_team_id ‘[[YOUR ITC TEAM ID]]’ # ID from the App Store Connect team</pre><p>These parameters are used so that Fastlane can target the developer, the app and the team. It is not obligatory to input any of these, as Fastlane will ask for all of the missing parameters anyway. Sometimes, it is even easier to not input some of these, as for example the <strong>team_id</strong> and the <strong>itc_team_id</strong> since Fastlane automatically finds and lists out all of a developer&#39;s teams.</p><p>After setting up the Appfile, we will move onto the Fastfile. Open it, remove everything and input the following:</p><pre>default_platform(:ios)<br>platform :ios do <br>  desc &quot;Creates a new app on both App Store Connect and the Apple Developer Portal&quot; <br>  lane :app_create do <br>    produce<br>  end <br>end</pre><p>In essence, this lane utilizes the <strong>produce</strong> command, in order to create a new app on the App Store Connect and Apple Developer sites with a fitting description. The lane is named <strong>app_create</strong>, but this is arbitrary and can be changed to whatever is most suitable.</p><p>Now navigate to the app directory in the terminal and run the command <strong>fastlane app_create</strong>. Fastlane will prompt the user to input an app name. Make sure it is unique. After the process successfully completes, log in to App Store Connect and the Apple Developer Portal and the new app should now be visible in both places.</p><p><strong>Generating Certificates and Provisioning Profiles</strong></p><p>After the application is created, it is time to generate the required certificates for the app.</p><p>The following are some benefits of using Fastlane in order to generate certificates:</p><ul><li>Saves time! Generating certificates manually is a tedious and dull process.</li><li>If the team decides on it, one account can be used throughout the team which will reduce the number of different provisioning profiles on the Apple Developer Portal keeping it a lot cleaner and easier to manage.</li></ul><p>Follow these steps in order to generate the certificates and provisioning profiles:</p><ol><li>Create one account which will be used by the entire time.</li><li>Fastlane utilizes Git Repos and Google Cloud Storages to store the certificates for the project in one centralized place. Create either one of these as well as copy the URL.</li><li>Run <strong>match init</strong>. This will prompt the user to input the URL from the previous step. The result of this command is a new file in the Fastlane folder called Matchfile. It is this file which is used as a reference for generating certificates and provisioning profiles.</li><li>Open the Matchfile, and input this:</li></ol><pre>git_url &#39;[[YOUR PRIVATE GIT REPO URL]]&#39; <br>app_identifier &#39;[[YOUR APP ID]]&#39; <br>username &#39;[[YOUR APPLE DEVELOPER PORTAL USERNAME]]&#39;</pre><p>5. Now run the following commands:</p><pre>fastlane match app store</pre><pre>fastlane match development</pre><p>This will create the development, App Store certificates and profiles for the application. Easy as pie.</p><p><strong>Deploy to Testflight with Fastlane</strong></p><p>After reaching a certain point in development, we’d like to deploy the app to a selected number of testers who can provide us with feedback. With Fastlane, it is possible to fully automate this release. Let’s do this by creating a simple lane for beta release:</p><pre>lane :beta do <br>  scan # run tests <br>  match(type: &quot;appstore&quot;) <br>  increment_build_number<br>  build_app(scheme: &quot;[[YOUR APP SCHEME]]&quot;) <br>  upload_to_testflight <br>end</pre><p>Run the <strong>fastlane beta</strong> command in order to execute the lane.</p><p>The idea behind it is to first run all the tests with the <strong>scan</strong> command since if they fail, Fastlane automatically stops the execution of the rest of the script.</p><p>The upload is now fully automated. However, if we were to log in to the App Store Connect, we would see that before actually submitting the app for beta release we would need to also input the test information for the app. Since Fastlane is used, it would be handy to also automate this input. In order to achieve this, the beta lane could look something like this:</p><pre>lane :beta do<br>  scan<br>  match(type: &quot;appstore&quot;)<br>  increment_build_number<br>  build_app(scheme: &quot;[[APP SCHEME]]&quot;)<br>  upload_to_testflight(<br>  localized_app_info: {<br>    &quot;default&quot;: {<br>    feedback_email: &quot;default@email.com&quot;,<br>    marketing_url: &quot;https://example.com/marketing-defafult&quot;,<br>    privacy_policy_url: &quot;https://example.com/privacy-defafult&quot;,<br>    description: &quot;Default description&quot;,<br>    }<br>  },<br>  beta_app_review_info: {<br>    contact_email: &quot;email@email.com&quot;,<br>    contact_first_name: &quot;firstname&quot;,<br>    contact_last_name: &quot;lastname&quot;,<br>    contact_phone: &quot;111222333444&quot;,<br>    demo_account_name: &quot;demo account name&quot;,<br>    demo_account_password: &quot;demo password&quot;,<br>    notes: &quot;This is a review note&quot;<br>  })<br>end</pre><p>Now when we run the <strong>fastlane beta</strong> command, all of the test information is uploaded to Testflight, in addition to the binary.</p><p>Note that the <strong>localized_app_info</strong> action may not work but remains in this blog for demonstration purposes.</p><p><strong>Deploy to App Store with Fastlane</strong><br>After the testers have reviewed the application, it is finally time to upload the app to the App Store. Now we’ll examine a number of steps in order to automate this:</p><ul><li>Creating the deliver file</li><li>Automating screenshots</li><li>Building and uploading to the App store</li></ul><p><strong>Creating the Deliver File</strong><br>Run <strong>fastlane init deliver</strong> in the command line. This will create a number of new folders and files in the Fastlane directory. This includes a Deliverfile, a metadata folder, and a screenshots folder. This is how the Fastlane folder currently looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*dega1XgRRAik7BTm.png" /></figure><p><strong>Illustration 2: Fastlane folder structure after running Fastlane init deliver</strong></p><p>The purpose of initializing the Deliver file is so that we can input all of the required metadata and screenshots locally, before submitting it to the App Store. This will then greatly help automate the process. Here is how the new metadata folder is structured:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*Npryh_HcGkrUuB0v.png" /></figure><p><strong>Illustration 3: new metadata folder</strong></p><p>Go through the metadata folder and input all of the different parameters. The en-US folder contains the app information for the English-US language. It is possible to input all of the app’s language in the same way, just using different language codes. The app’s metadata is now ready to be uploaded.</p><p><strong>Automating Screenshots</strong></p><p>Fastlane takes advantage of Apple’s UITesting framework in order to automate screenshots. The basic logic behind it is to run UITests and when a certain point in the test is reached, Fastlane’s snapshot function should be used to capture a screenshot. For example, you can take a screenshot after the UITest executes typing in a username text field on a login screen like this:</p><pre>userNameTextfield.typeText(&quot;Username&quot;) <br>snapshot(&quot;01LoginScreen&quot;)</pre><p>We will not be covering how to write tests for automating the screenshots but there are many tutorials online and it’s a fairly straightforward process.</p><p>In order to set up automated screenshots we can do the following:</p><ul><li>Run <strong>fastlane snapshot init</strong> in the project directory. This will create two new files in the Fastlane folder; one called Snapfile and the other one called SnapshotHelper.swift.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*CjuSYPRhqNAnhdwb.png" /></figure><p><strong>Illustration 4: Snapfile and SnapshotHelper.swift</strong></p><ul><li>Go into the Xcode project and navigate to File -&gt; New -&gt; Target. In the pop-up that appears, find the iOS UI Testing Bundle and press next.</li><li>On the new screen, change the name of the UITests or leave everything as it is and press finish.</li><li>A new folder in the XCode project with the UITests is created. Find the previously created SnapshotHelper.swift and drag and drop it into the new UITests Folder. Note: Make sure to copy it correctly by selecting both the “Copy items if needed” and the UITest target button and then deselecting the project target.</li><li>Open “Manage Schemes” in the Xcode project and make sure that both the “Show” and “Shared” checkboxes for the created UITest Schemes are checked.</li><li>In the same window click on the newly created UITest Scheme and press “edit” and then in the new window, window press “Build”.</li><li>This will show the UITest Target with a number of checkboxes. Make sure the checkboxes named “Test” and “Run” are checked. Fastlane can now access the UITest target scheme.</li><li>Open the Snapfile, and input this:</li></ul><pre>devices([ &quot;iPhone X&quot;, &quot;iPhone 8&quot; ]) <br>languages([&#39;en-US&#39;]) <br>scheme(&quot;[[YOUR UITEST SCHEME]]&quot;) <br>output_directory &quot;./fastlane/screenshots&quot; clear_previous_screenshots(true)</pre><ul><li>Now everything is ready for you to capture the screenshots. Input these lines of code in your UITest function in order to utilize the SnapshotHelper.swift:</li></ul><pre>let app = XCUIApplication() <br>setupSnapshot(app) <br>app.launch()</pre><p>As I mentioned before, we’ll not be covering the actual writing of the UITests since every application has different and specific screens. Therefore, it is the reader’s task to now create the UITests to automate the screenshots of the app.</p><p>After writing the tests, run <strong>fastlane snapshot</strong> in the terminal and if everything is set up correctly, the screenshots will be taken.</p><h3>Building and Uploading to the App Store</h3><p>With the deliver file created and screenshots automated, the next step is to upload everything to App Store Connect. A couple of lanes will be individually created for each of the tasks required for the release and then combined together in order to make one lane for the entire release process.</p><p><strong>The first lane is for testing:</strong></p><pre>lane :test do <br>  desc &quot;Run tests&quot; <br>  scan <br>end</pre><p><strong>The next lane is for taking screenshots:</strong></p><pre>lane :screenshots do <br>  desc &quot;Take screenshots&quot; <br>  snapshot <br>end</pre><p><strong>The third lane is for building the application:</strong></p><pre>lane :build do <br>  desc &quot;Build application&quot; <br>  increment_build_number({ <br>    build_number: latest_testflight_build_number + 1 <br>  }) <br>  build_ios_app(<br>    scheme: &quot;[[YOUR APP SCHEME]]&quot;<br>  ) <br>end</pre><p><strong>increment_build_number</strong> checks the latest Testflight build number and increments this build number by 1. This is better than incrementing automatically because sometimes the binary is not uploaded to the App Store/Testflight because of an error, but the build number still gets incremented. Bear in mind, that there must be at least one build on Testflight in order to run the <strong>latest_testflight_build_number</strong> command.</p><p><strong>The fourth lane is to upload the binary:</strong></p><pre>lane :upload do <br>  desc &quot;Upload metadata, screenshots and binary&quot; <br>  deliver( <br>    force: true, <br>    automatic_release: true, <br>  ) <br>end</pre><p>The deliver command is an alias for the <strong>upload_to_app_store</strong> action and is used to upload the metadata, screenshots and binary to the App Store. The <strong>force: true</strong> command is for skipping the HTML preview of the metadata and the <strong>automatic_release: true</strong> command is to ensure automatic release after the application is reviewed on App Store Connect.</p><p><strong>Now all of this can be combined into a single lane called release:</strong></p><pre>lane :release do <br>  desc &quot;Run tests, take screenshots, upload deliver file, upload app&quot; <br>  ensure_git_status_clean <br>  test <br>  match(type: &quot;appstore&quot;) <br>  screenshots <br>  build <br>  upload <br>end</pre><p>In addition to the created lanes, the match command is added in order to make sure that the certificates are up-to-date and the <strong>ensure_git_status_clean</strong> is used to make sure that you are working with a clean Git Repo. With this setup, the version number must be manually incremented. Keep in mind that Fastlane has actions for automatically incrementing version numbers. View <a href="https://docs.fastlane.tools/actions/increment_version_number/">this link</a> for more information.</p><p>Navigate to the project directory and run <strong>fastlane release</strong> and watch the magic happen!</p><h3>Concluding Thoughts</h3><p>As you can see from this blog, Fastlane is a powerful tool used for automated deployment. Once you become comfortable using it, the scripts and automation tasks will become more advanced and suited for your exact needs. If you feel hesitant about giving it a try, just start with small automation tasks and build upon that. After some time, it will definitely become an important tool in your toolbox.</p><p><em>Originally published at </em><a href="https://www.rubicon-world.com/blog/2019/05/automated-deployment-with-fastlane-on-ios/"><em>https://www.rubicon-world.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef9a72898947" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rubicon-stories/automated-deployment-with-fastlane-on-ios-rubicon-ef9a72898947">Automated Deployment with Fastlane on iOS | RUBICON</a> was originally published in <a href="https://medium.com/rubicon-stories">RUBICON Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>