Omax Tech | Blog | Automating Screenshot Uploads to App Store Connect with GitHub Actions

Automating Screenshot Uploads to App Store Connect with GitHub Actions

Cloud/Devops
Sep 26, 2025
5-6 min

Share blog

Introduction

In iOS development, building an app and manually capturing screenshots for multiple devices can be a tedious and time-consuming task. Automating these processes using DevOps automation helps streamline the workflow, especially when dealing with multiple screen sizes and languages.

This blog post demonstrates how to automate the entire process-building the app, launching it in an iOS Simulator, capturing screenshots, and uploading them to App Store Connect. Leveraging App Store Connect’s API, this CI/CD pipeline can save time, ensure consistency, and improve efficiency during app release.

Why Automate?

Manually building apps, launching them in simulators, and capturing screenshots can be tedious. This becomes even more challenging when managing multiple devices and scenarios. GitHub Actions provides a platform to automate these tasks by creating a workflow that does everything from setting up dependencies to building, launching, and taking screenshots of your app.

Step-by-Step Guide

Here’s how I built this automation pipeline:

1. Setting Up the Workflow

We start by defining the GitHub Actions workflow file (iOS_Screenshot_Upload.yml). This file outlines the steps the workflow will take whenever changes are pushed to a specific branch (e.g., ScreenshotBuild).

Omax Tech | Blog | Image

This ensures that the workflow triggers when code is pushed to the ScreenshotBuild branch.

2. Environment Setup

Setting up the environment is the next critical step. We need Python, Ruby (for CocoaPods), and Node.js for React Native dependencies.

Omax Tech | Blog | Image

We also use CocoaPods for dependency management in iOS and cache them to speed up subsequent builds.

Omax Tech | Blog | Image

3. Installing and Updating Pods

We integrate CocoaPods with our project by updating and installing the necessary dependencies:

Omax Tech | Blog | Image

4. Building the App

To simulate the app on a specific device, we build the app for the iOS Simulator (in this case, using the iPhone 14). Before building, we clean the build folder and Derived Data:

Omax Tech | Blog | Image

This step compiles the app and prepares it for installation on the simulator.

5. Booting the Simulator and Launching the App

After successfully building the app, we find the UUID of the desired simulator, boot it, and install the app.

Omax Tech | Blog | Image

The app is launched using its Bundle ID.

6. Capturing the Screenshots

Screenshots are captured using UUID of emulator and path defined to save screenshot as desired place.

Omax Tech | Blog | Image

7. Uploading and Downloading Screenshots

The screenshots are uploaded as artifacts so that they can be easily accessed:

Omax Tech | Blog | Image

To download them later, we use the download-artifact action:

Omax Tech | Blog | Image

8. Create Screenshot Set

The first API request is responsible for creating a new screenshot set associated with a specific app version on App Store Connect. A screenshot set groups screenshots that are specific to a particular display type, like for iPhones, iPads, or other devices.

Let's Build Something Great Together

Ready to transform your idea into a powerful software solution? Talk to our experts and get a free consultation.

Contact Us
  • URL: /v1/appScreenshotSets
  • Request Type: POST
  • Description: This API creates a screenshot set for a specific app version localization.
  • Payload: It includes details such as screenshotDisplayType, which specifies the type of screenshots (e.g., iPhone 6.7″ display), and the ID of the app’s version localization.
  • Response: The API returns an ID for the newly created screenshot set, which is later used to upload screenshots to this set.
Omax Tech | Blog | Image

9. Upload Screenshots to App Store Connect

Once the screenshot set is created, this API request uploads screenshots to the App Store Connect. The process is divided into two steps: creating an entity for each screenshot and uploading the actual image file.

  • URL: /v1/appScreenshots
  • Request Type: POST
  • Description: This API request initiates the upload process by creating an app screenshot entity. It defines the filename, file size, and links it to the appScreenshotSet.
  • Response: The response contains details like the upload URL and Content-Type headersneeded for the next step, along with the screenshotId, which uniquely identifies the screenshot.
Omax Tech | Blog | Image

10. Upload Screenshot File

After creating the screenshot entity, the next API call uploads the actual image file to the provided URL.

  • URL: The URL is dynamically provided in the previous response (uploadUrl).
  • Request Type: PUT
  • Description: This API uploads the screenshot image to the App Store Connect servers. It uses the Content-Type header specified earlier, and the image file itself is uploaded to the provided URL.
  • Response: This step confirms the upload of the screenshot file to the server.
Omax Tech | Blog | Image

11. Commit Screenshot Reservation

Finally, after uploading the screenshot, the reservation for the uploaded screenshot needs to be committed to App Store Connect. This ensures the screenshot is marked as uploaded and ready for review.

  • URL: /v1/appScreenshots/{screenshotId}
  • Request Type: PATCH
  • Description: This API marks the screenshot upload as complete by committing the reservation. The payload includes the MD5 checksum of the uploaded file to verify its integrity.
  • Response: The API responds with the status of the screenshot reservation, confirming that the screenshot is now available for the app version on the App Store.
Omax Tech | Blog | Image
Omax Tech | Blog | Image

Conclusion

By automating the iOS app testing and screenshot capture process, developers can avoid repetitive manual tasks and focus more on enhancing app features. This GitHub Actions workflow demonstrates how to build, launch, and capture screenshots on an iOS Simulator, followed by uploading those screenshots directly to App Store Connect. With this setup, you can easily extend automation to cover additional devices and screen variations, or even other App Store Connect tasks such as submitting apps for review.

Integrating automation into your development process can enhance productivity, minimize errors, and streamline app store submissions, making your iOS development lifecycle much smoother.

Blogs

Discover the latest insights and trends in technology with the Omax Tech Blog.

View All Blogs
Omax Tech | Blog | When AI Tests the Software, Who Owns the Quality?
12-15 min
November 11, 2026

When AI Tests the Software, Who Owns the Quality?

AI can execute thousands of tests, but can it own quality? Exploring why quality remains a shared human responsibility even as AI automates testing.

Read More
Omax Tech | Blog | From ETL to ELT: The Evolution of Data Pipelines in Modern Analytics
12-15 min
October 16, 2026

From ETL to ELT: The Evolution of Data Pipelines in Modern Analytics

How and why data pipeline architecture evolved from ETL to ELT.

Read More
Omax Tech | Blog | Bridge View Hybrid: A Smarter Path to Bringing Web Apps to Mobile
8-10 min
October 06, 2026

Bridge View Hybrid: A Smarter Path to Bringing Web Apps to Mobile

Learn how the Bridge View Hybrid architecture uses a React Native shell and WebView to launch iOS and Android apps faster, cheaper, and with less risk.

Read More
Omax Tech | Blog | 10 AI Prompts Every Manual Tester Should Have in Their QA Toolkit
10-12 min
September 30, 2026

10 AI Prompts Every Manual Tester Should Have in Their QA Toolkit

Discover 10 practical AI prompts manual testers can use to improve test coverage, find edge cases, analyze bugs, strengthen regression testing, and become more effective QA engineers.

Read More
Omax Tech | Blog | The Website Accessibility Revolution: Why You Can't Afford to Ignore WCAG 2.2
8-10 min
September 29, 2026

The Website Accessibility Revolution: Why You Can't Afford to Ignore WCAG 2.2

Website accessibility starts with WCAG 2.2. Learn how accessible design, development, QA, and testing can help create websites that work for everyone.

Read More
Omax Tech | Blog | Race Conditions in Web Applications: Why Correct Code Produces Wrong Results
10-12 min
September 21, 2026

Race Conditions in Web Applications: Why Correct Code Produces Wrong Results

Race conditions silently corrupt data when concurrent requests touch shared state at the wrong time. Learn how atomic updates, transactions, idempotency, and locking keep your application correct under real concurrency.

Read More
Omax Tech | Blog | AI Writes the Code • Stop Blindly Shipping It Without Reviewing the Engineering
8-10 min
September 17, 2026

AI Writes the Code • Stop Blindly Shipping It Without Reviewing the Engineering

A practical perspective on AI-generated code, scalability, maintainability, and engineering judgment and why engineering review still owns the final decision.

Read More
Omax Tech | Blog | Migrating Databases with AWS DMS With Nearly Zero Downtime
10-15 min
September 14, 2026

Migrating Databases with AWS DMS With Nearly Zero Downtime

Learn how to migrate databases using AWS DMS with nearly zero downtime using Full Load, CDC, validation, monitoring, and controlled cutover.

Read More
Omax Tech | Blog | How to Add LiveKit Video Calling to a Next.js App
12-14 min
September 11, 2026

How to Add LiveKit Video Calling to a Next.js App

Add embedded video & audio calling to Next.js with LiveKit Cloud. Compared vs Twilio, Daily, Agora, Zoom — plus token auth, guests & recording.

Read More