codemagic-ci-cd / codemagic-sample-projects

A collection of sample apps built with Codemagic CI/CD. Please see the codemagic.yaml file for a sample workflow configuration.

Codemagic Sample Projects

Flutter

• Flutter Android and iOS
• Flutter macOS sample
• Flutter Windows sample

Android native

• Android sample project

iOS native

• iOS sample project

React Native

• React Native Android and iOS
• React Native using Expo without ejecting

Unity

• Unity Android, iOS, Windows, and macOS sample
• Steam Publishing sample

Other platforms

Click to expand...

Ionic Samples

• Ionic + Capacitor sample
• Ionic + Cordova sample

Kotlin Multiplatform Mobile Samples

• KMM sample

.NET MAUI Samples

• .NET MAUI Android and iOS

---

Integrations

Crash reporting

• Firebase Crashlytics
• Sentry

Code quality

• Codecov
• SonarQube / SonarCloud (iOS)
• SonarQube / SonarCloud (Android)
• Emerge Tools

Messaging

• Discord

Project management

• Jira

Testing

• emulator.wtf
• Katalon

Real-device testing

• Appetize
• BrowserStack (App Live)
• BrowserStack (App Automate)
• Kobiton
• LambdaTest
• pCloudy
• Sofy

Other

• Capgo

Older sample projects

Flutter Samples

• Flutter integration tests
• Flutter flavors sample

iOS (Native) Samples

• iOS Automatic code signing sample
• iOS Manual code signing sample
• iOS White label single scheme sample
• iOS Magic Actions sample

Android (Native) Samples

• Android with espresso testing sample

React Native Samples

• React Native detox sample

Integrations

• Fastlane integration sample

YAML Samples

• YAML anchors and aliases sample

Cordova Samples

• Cordova sample

Getting help and support

If you have a technical question or need help with some particular issue, you can get help on our GitHub discussions page.

Customers who have enabled billing can use the in-app chat widget to get support. You must be logged in to see the chat icon at the bottom right corner (please note that some adblockers might block the chat widget).

Raising issues

If there are any use cases that are not covered in the sample projects you can create an issue to request them:

https://github.com/codemagic-ci-cd/codemagic-sample-projects/issues

codemagic-sample-projects's Issues

exited with status code 1

Hello there I am integrating the Codemagic in my iOS App.

I am getting exited with status code 1 error at scripts when doing pod install.

like,

scripts:
- name: Install pods
script: |
pod install

BUILD_NUMBER is used for both build number and minor version

Describe the sample projects update you'd like to see
In the sample yaml for flutter (flutter/flutter-android-and-ios-yaml-demo-project/codemagic.yaml) , the BUILD_NUMBER is correctly retrieved from google play but is then incorrectly used as both the minor version of the app version number and the build number.

BUILD_NUMBER=$(($(google-play get-latest-build-number --package-name "$PACKAGE_NAME" --tracks="$GOOGLE_PLAY_TRACK") + 1))      
          flutter build appbundle --release \
            --build-name=1.0.$BUILD_NUMBER \
            --build-number=$BUILD_NUMBER

I think it would be more correct if the BUILD_NUMBER variable were only used for the --build-number setting. the build-name is meant to change less frequently and could either be hard coded by the user of the template or retrieved in a seperate call to google-play (couldn't find such a call)....

BUILD_NUMBER=$(($(google-play get-latest-build-number --package-name "$PACKAGE_NAME" --tracks="$GOOGLE_PLAY_TRACK") + 1))      
          flutter build appbundle --release \
            --build-name=1.0.CHANGE_THIS_YOURSELF \
            --build-number=$BUILD_NUMBER

Additional context
Note in the screenshot the build number (4) is both the minor version and the build number. this is incorrect, the scripting should have produced 1.02 with a latest version of 4.

Getting support
Support for customers who haven't enabled billing is available in the Discussions section of our Documentation repository.

If you have enabled billing in Codemagic, you can contact the support team directly using the in-app chat widget.

Unity CCD - flag needs an argument: --environment

we are facing issue regarding Cloud Content Delivery. We followed this tutorial.
How to deploy game updates with Unity Cloud Content Delivery and Codemagic
Codemagic is now showing error "flag needs an argument: --environment"
All IDs are added to environment variable already.

#!/usr/bin/env bash
ucd entries sync PricklyBear/AssetBundles/Android --apikey $ {CCD_API_KEY} --bucket $ {CCD_BUCKET_ID} --environment $ {CCD_ENVIRONMENT_ID}
ucd releases create --apikey $ {CCD_API_KEY} --bucket $ {CCD_BUCKET_ID} --environment $ {CCD_ENVIRONMENT_ID}
flag needs an argument: --environment
flag needs an argument: --environment
Build failed :|
Step 2 script Login+Sync CCD exited with status code 1

Request for adding Codemagic App Preview to Codemagic Sample projects

Hey 👋

This is a request to add a sample that uses the Codemagic App Preview tool. It's a free and open-source tool built on top of Codemagic that improves the pull request review process.

I could create a pull request for that and maintain it, that's not a problem. However, you need to decide if this something you want to have in your samples project since it's not an official Codemagic tool.

Please don't hesitate to deny this request.

React Native sample project doesn't show release signing in build.gradle

Sample should show how to add the release signing config to app/android/build.gradle

Add Example for Testlab and IOS

I'm currently trying to add testlab to my flutter integration tests.
There are examples about how to do it with Android but none about IOS.

script `Build .ipa` exited with status code 65

I am stuck here

here is a script in my yaml file

- name: Build .ipa script: | xcode-project build-ipa --workspace "$XCODE_WORKSPACE" --scheme "$XCODE_SCHEME"

Flutter yaml samples without `instance_type` throws an error

When copying codemagic.yaml from Flutter YAML sample and run it in my project it throws following error:

I had to fix this by specifying instance type instance_type: mac_mini_m1 and run the build again.

Readme files seem to contain old info about securing environment variables

Some readme files have the following:

Encrypted Environment Variables
Use the Codemagic web app to securely encrypt environment variables that are included in the codemagic.yaml. These values can only be accessed on the Codemagic build servers.

Please note that encrypted values are specific to your personal account or team. If you move your app from personal account to a Team or vice versa you will need to re-encrypt these values.

Let's revise current repos and update with new approach where variables are defined in Codemagic application in team level, app level and workflow level.

Encryption API remains active, but seems better to keep it simple in these cases.

Update Flutter samples

Looks like all the Flutter samples currently have flutter build apk --release

For instance

codemagic-sample-projects/Firebase-App-Distribution/codemagic_firebase_app_distribution_yaml-master/codemagic.yaml

Line 50 in d1e842b

cd . && flutter build apk --release --build-name=1.0.0 --build-number=$(($(google-play get-latest-build-number --package-name "$PACKAGE_NAME") + 1))

Google requires an app bundle for publishing new apps from Aug 2021.

https://android-developers.googleblog.com/2021/06/the-future-of-android-app-bundles-is.html

Also, Flutter docs prefer app bundles too.
https://docs.flutter.dev/deployment/android#building-the-app-for-release

Solution

Update all Flutter samples including this

This needs a README file

Here at least: https://github.com/codemagic-ci-cd/codemagic-sample-projects/tree/main/ios/ios-automatic-code-signing-demo-project

No artifacts were found in Unity Build

Hi, We are facing issue in artifacts section in codemagic.yaml file. Everything is just fine but wen creating build it says

== Gathering artifacts ==
No artifacts were found

articats are mentioned in yaml file. We followed these guidelines to create Unity application
Building Unity mobile apps

Please help what could be the issue.