.NET MAUI App Store Deployment Pipeline Setup
Budget: $30 – $250 USD
Set Up Full App Store & Google Play Deployment Pipeline for .NET MAUI App
(From Scratch)
OVERVIEW
I am looking for an experienced mobile DevOps / CI/CD engineer to take my .NET MAUI app from a working Visual Studio project all the way to live deployments on both the Apple App Store and Google Play Store — completely from scratch.
I currently have zero presence on either store. No certificates, no provisioning profiles. Nothing.
I can build and deploy to physical Android and iOS devices in Debug mode from Visual Studio, and that is all.
By the end of this project, both apps must be live in their respective stores (internal test track is acceptable for initial delivery), and an automated GitHub Actions pipeline must be in place so that any future push to the main branch on GitHub automatically builds, signs, and deploys both apps without any manual steps.
ABOUT THE APP
- Framework: .NET MAUI (C#), Visual Studio 2022
- SDK: .NET 10.0 (net10.0-android, net10.0-ios, net10.0-maccatalyst, net10.0-windows10.0.19041.0)
- Two apps in one solution:
- ReQ — consumer-facing roadside assistance app
- ResQ Provider — provider-facing roadside assistance app
- Repository: Private GitHub repo (roadresqservice/RoadRescuePlatform)
- Platform: Currently builds and runs on physical Android and iOS devices in Debug mode from Visual Studio
WHAT NEEDS TO BE DONE — FULL SCOPE
The freelancer is responsible for everything listed below. I will provide access to accounts but have no existing setup on any platform.
GOOGLE PLAY (ANDROID)
- Create and configure the app listing in Google Play Console (both apps)
- Generate and configure the Android keystore for release signing
- Configure the app bundle identifier / package name
- Build a release-signed AAB (Android App Bundle) targeting API level 35
- Upload the initial AAB manually to Google Play Console (required for first upload)
- Set up Google Play internal test track
- Create a Google Play service account with the correct API permissions for automated uploads
- Set up GitHub Actions workflow (deploy-android.yml) that triggers on push to main and uploads the signed AAB to the internal track automatically
APPLE APP STORE (iOS)
- Create the App IDs in the Apple Developer portal for both apps
- Generate an Apple Distribution certificate
- Create App Store provisioning profiles for both apps
- Create the app records in App Store Connect for both apps
- Build and sign a release IPA
- Upload the initial IPA to App Store Connect (TestFlight internal testing is acceptable for initial delivery)
- Create an App Store Connect API key (p8 file) for automated uploads
- Set up GitHub Actions workflow (deploy-ios.yml) that triggers on push to main, builds and signs the IPA on our Mac, and uploads it to App Store Connect automatically
GITHUB ACTIONS — SELF-HOSTED RUNNERS
- Register our Windows PC (NucBox M6Ultra) as a self-hosted GitHub Actions runner for Android builds
- Register our Mac (always on, local network at 192.168.4.197) as a self-hosted GitHub Actions runner for iOS builds
- Verify both runners appear online in the GitHub repository settings before delivery
IMPORTANT NOTE ON .NET 10.0
The project targets .NET 10.0 MAUI. You must verify that the self-hosted runner environments (Windows PC and Mac) have .NET 10.0 SDK installed and that the GitHub Actions workflows use the correct SDK version. Do not assume .NET 8 or .NET 9. Confirm SDK availability before starting.
DELIVERABLES
The following must be delivered before payment is released:
1. Both apps successfully uploaded to their respective stores (Google Play internal track and App Store Connect / TestFlight)
2. deploy-android.yml — GitHub Actions workflow file committed to the repository
3. deploy-ios.yml — GitHub Actions workflow file committed to the repository
4. GitHub Secrets reference document — a list of every secret name used in the workflows, what each one contains, and how to obtain it (secret VALUES are not included — I will enter those myself)
5. Runner setup guide — step-by-step instructions for registering the Windows PC and Mac as self-hosted runners, in case I need to re-register them in the future
6. Code signing guide — document explaining the keystore, certificates, and provisioning profiles used, where they are stored, and how to renew them when they expire
7. End-to-end test — push a commit to main and confirm both pipelines complete successfully and a new build appears in both stores
SECURITY REQUIREMENTS — PLEASE READ
- Do NOT commit any credentials, passwords, API keys, certificates, or keystores to the GitHub repository. All sensitive values go into GitHub Secrets only.
- Do NOT modify any application source code.
- Do NOT merge anything into the main branch without my explicit approval.
- Do NOT request Owner or Admin access to the GitHub repository. You will receive Write access to the develop branch only.
- Do NOT request access to my personal Apple ID, Google account, or any financial accounts.
- All access granted during the project will be revoked upon completion.
REQUIRED SKILLS
- GitHub Actions — workflow authoring, self-hosted runners, secrets management
- .NET MAUI — release builds on .NET 10.0, code signing, AAB and IPA generation
- Google Play Developer API — service account setup, automated AAB upload
- Apple App Store Connect API — p8 API key auth, IPA upload via altool or fastlane
- Android code signing — keystore generation and management
- Apple code signing — Distribution certificates, App IDs, provisioning profiles
- PowerShell and/or Bash scripting
NICE TO HAVE
- Experience with fastlane for iOS automation
- Experience with .NET 10.0 MAUI specifically
- Experience setting up App Store and Google Play listings from scratch
ACCESS I WILL PROVIDE
- GitHub collaborator access (Write) to the develop branch
- Apple Developer account access (temporary, for certificate and provisioning profile setup)
- App Store Connect access — App Manager role
- Google Play Console access — Release Manager role scoped to these apps
- Temporary SSH or remote access to the Mac build agent if needed
BUDGET AND TIMELINE
- Fixed price only — please include your quote in your proposal
- Expected timeline: 7 to 10 business days
- Payment is milestone-based and will only be released after a successful end-to-end test deployment confirmed by me personally
HOW TO APPLY
Please include the following in your proposal or I will not consider it:
1. Your specific experience with .NET MAUI app store deployments (mention the .NET version you have worked with)
2. Your experience setting up GitHub Actions pipelines for mobile apps
3. Links to similar projects you have completed (app store deployments, CI/CD pipelines)
4. Your fixed price quote
5. Your estimated timeline broken down by phase (store setup, signing, pipeline, testing)
Proposals that are generic, do not mention MAUI or mobile CI/CD, or do not include a price will be declined.
(From Scratch)
OVERVIEW
I am looking for an experienced mobile DevOps / CI/CD engineer to take my .NET MAUI app from a working Visual Studio project all the way to live deployments on both the Apple App Store and Google Play Store — completely from scratch.
I currently have zero presence on either store. No certificates, no provisioning profiles. Nothing.
I can build and deploy to physical Android and iOS devices in Debug mode from Visual Studio, and that is all.
By the end of this project, both apps must be live in their respective stores (internal test track is acceptable for initial delivery), and an automated GitHub Actions pipeline must be in place so that any future push to the main branch on GitHub automatically builds, signs, and deploys both apps without any manual steps.
ABOUT THE APP
- Framework: .NET MAUI (C#), Visual Studio 2022
- SDK: .NET 10.0 (net10.0-android, net10.0-ios, net10.0-maccatalyst, net10.0-windows10.0.19041.0)
- Two apps in one solution:
- ReQ — consumer-facing roadside assistance app
- ResQ Provider — provider-facing roadside assistance app
- Repository: Private GitHub repo (roadresqservice/RoadRescuePlatform)
- Platform: Currently builds and runs on physical Android and iOS devices in Debug mode from Visual Studio
WHAT NEEDS TO BE DONE — FULL SCOPE
The freelancer is responsible for everything listed below. I will provide access to accounts but have no existing setup on any platform.
GOOGLE PLAY (ANDROID)
- Create and configure the app listing in Google Play Console (both apps)
- Generate and configure the Android keystore for release signing
- Configure the app bundle identifier / package name
- Build a release-signed AAB (Android App Bundle) targeting API level 35
- Upload the initial AAB manually to Google Play Console (required for first upload)
- Set up Google Play internal test track
- Create a Google Play service account with the correct API permissions for automated uploads
- Set up GitHub Actions workflow (deploy-android.yml) that triggers on push to main and uploads the signed AAB to the internal track automatically
APPLE APP STORE (iOS)
- Create the App IDs in the Apple Developer portal for both apps
- Generate an Apple Distribution certificate
- Create App Store provisioning profiles for both apps
- Create the app records in App Store Connect for both apps
- Build and sign a release IPA
- Upload the initial IPA to App Store Connect (TestFlight internal testing is acceptable for initial delivery)
- Create an App Store Connect API key (p8 file) for automated uploads
- Set up GitHub Actions workflow (deploy-ios.yml) that triggers on push to main, builds and signs the IPA on our Mac, and uploads it to App Store Connect automatically
GITHUB ACTIONS — SELF-HOSTED RUNNERS
- Register our Windows PC (NucBox M6Ultra) as a self-hosted GitHub Actions runner for Android builds
- Register our Mac (always on, local network at 192.168.4.197) as a self-hosted GitHub Actions runner for iOS builds
- Verify both runners appear online in the GitHub repository settings before delivery
IMPORTANT NOTE ON .NET 10.0
The project targets .NET 10.0 MAUI. You must verify that the self-hosted runner environments (Windows PC and Mac) have .NET 10.0 SDK installed and that the GitHub Actions workflows use the correct SDK version. Do not assume .NET 8 or .NET 9. Confirm SDK availability before starting.
DELIVERABLES
The following must be delivered before payment is released:
1. Both apps successfully uploaded to their respective stores (Google Play internal track and App Store Connect / TestFlight)
2. deploy-android.yml — GitHub Actions workflow file committed to the repository
3. deploy-ios.yml — GitHub Actions workflow file committed to the repository
4. GitHub Secrets reference document — a list of every secret name used in the workflows, what each one contains, and how to obtain it (secret VALUES are not included — I will enter those myself)
5. Runner setup guide — step-by-step instructions for registering the Windows PC and Mac as self-hosted runners, in case I need to re-register them in the future
6. Code signing guide — document explaining the keystore, certificates, and provisioning profiles used, where they are stored, and how to renew them when they expire
7. End-to-end test — push a commit to main and confirm both pipelines complete successfully and a new build appears in both stores
SECURITY REQUIREMENTS — PLEASE READ
- Do NOT commit any credentials, passwords, API keys, certificates, or keystores to the GitHub repository. All sensitive values go into GitHub Secrets only.
- Do NOT modify any application source code.
- Do NOT merge anything into the main branch without my explicit approval.
- Do NOT request Owner or Admin access to the GitHub repository. You will receive Write access to the develop branch only.
- Do NOT request access to my personal Apple ID, Google account, or any financial accounts.
- All access granted during the project will be revoked upon completion.
REQUIRED SKILLS
- GitHub Actions — workflow authoring, self-hosted runners, secrets management
- .NET MAUI — release builds on .NET 10.0, code signing, AAB and IPA generation
- Google Play Developer API — service account setup, automated AAB upload
- Apple App Store Connect API — p8 API key auth, IPA upload via altool or fastlane
- Android code signing — keystore generation and management
- Apple code signing — Distribution certificates, App IDs, provisioning profiles
- PowerShell and/or Bash scripting
NICE TO HAVE
- Experience with fastlane for iOS automation
- Experience with .NET 10.0 MAUI specifically
- Experience setting up App Store and Google Play listings from scratch
ACCESS I WILL PROVIDE
- GitHub collaborator access (Write) to the develop branch
- Apple Developer account access (temporary, for certificate and provisioning profile setup)
- App Store Connect access — App Manager role
- Google Play Console access — Release Manager role scoped to these apps
- Temporary SSH or remote access to the Mac build agent if needed
BUDGET AND TIMELINE
- Fixed price only — please include your quote in your proposal
- Expected timeline: 7 to 10 business days
- Payment is milestone-based and will only be released after a successful end-to-end test deployment confirmed by me personally
HOW TO APPLY
Please include the following in your proposal or I will not consider it:
1. Your specific experience with .NET MAUI app store deployments (mention the .NET version you have worked with)
2. Your experience setting up GitHub Actions pipelines for mobile apps
3. Links to similar projects you have completed (app store deployments, CI/CD pipelines)
4. Your fixed price quote
5. Your estimated timeline broken down by phase (store setup, signing, pipeline, testing)
Proposals that are generic, do not mention MAUI or mobile CI/CD, or do not include a price will be declined.