What are all these "out.aar" assets files?

[burekas7]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

Hi,

According to this build:
https://codemagic.io/app/636d13b239a6170009d6aedd/build/6964e96407d8ddd4707dc8fa

1. What are all these generated strange out.aar files? It wasn't like this before.

2. And I know you asked elsewhere and I still haven't implemented some of the things.
   But why is the Android build taking so much time? 11 minutes!
   Even in the past, when I hadn't implemented some of those suggestions, it wasn't this excessive.

It would be one thing if I were a private individual with free minutes, but here we are paying for this time.

Thanks for help.

[Becca-Saka]

Hello @burekas7

1. The AAR is generated by plugins used in your project, unfortunately, there is no direct way via WFE to stop exporting them. You can switch to codemagic.yaml and add the outputs you'd like to see, for example

 artifacts:
      - build/ios/ipa/*.ipa
      - /tmp/xcodebuild_logs/*.log
      - flutter_drive.log 

2. To help speed up builds, I suggest enabling caching in your workflow configuration for Gradle and pub:
   using WFE

or codemagic.yaml

   android-workflow:
        name: Android Workflow
        max_build_duration: 120
        instance_type: mac_mini_m2
        cache:
          cache_paths:
            - $HOME/.gradle/caches
            - $HOME/.pub-cache

This way, your workflow won't need to download dependencies every time you build.
Please note, caching only takes effect after a successful build, so you'll need at least one build to go through before it starts helping. You should see a notable difference in build time. You can read more about caching here

Let me know if this helps.

[Becca-Saka]

Yes, there are the most relevant ones.

it should be $HOME, CM_BUILD_DIR is your project path.

[burekas7]

@Becca-Saka

Ok I did it, this is the second build, but I still don't see any improve:
https://codemagic.io/app/636d13c539a617000f89bf6e/build/6967a98186cfae42d7bd6653

Android build is 9 minutes! (while iOS build is less then 2 minutes)
Total process time 19 minutes!

Some time ago the total build process time was around 12 minutes (both Android & iOS)

[Becca-Saka]

@burekas7

1. As I highlighted in my first message, the caching doesn't take effect until after your first successful build, so I believe you should see a change in the next build, because the cache was created on this build.

2. The build time is dependent on your dependencies and your project. We do not have control over this, we can only help you optimize which is the tip I sent earlier about the caching. You can run a Profile Build to Analyse what the Bottlenecks are
   This helps pinpoint which build steps or dependencies are causing delays.
   To enable this, you may need to switch to yaml configuration and add the following snippet to your build configuration:

- name: Profile Android Build
    script: | 
      ./gradlew bundleRelease --profile -PversionCode=$(($BUILD_NUMBER + 600)) -Dorg.gradle.jvmargs="-Xmx4096m"
      ./gradlew assembleRelease --profile -PversionCode=$(($BUILD_NUMBER + 600)) -Dorg.gradle.jvmargs="-Xmx4096m"

  artifacts:
    - /*.zip
    - builder/**.zip

Once the build is complete, you’ll get a report highlighting which tasks took the most time. Here’s an example of what the result might look like: profile_build.html

But I believe the caching should help you, let me know if it does.

[Becca-Saka]

Hello @burekas7 checking in on this, how did this go?

[burekas7]

@Becca-Saka
Hi,
I will update as soon as I prepare the next build.
Thank you.