zirouan / fastfileexamples

Here you can see a short example of Fastfiles (fastlane file that contains the famous lanes) to Android

FastfileExamples

Here you can see a short example of Fastfiles (fastlane file that contains the famous lanes) to Android

Any Platform

Type "live" the release note

In the beginning of fastlane execution, a prompt is shown, waiting the release notes of the current version be typed. To do this, its simple:

release_notes = prompt(
                  text: "Release notes: ",
                  multi_line_end_keyword: "END"
                )

When prompt receives the value of the key multi_line_end_keyword, it will close and save the result (without the end keyword) in release_notes variable to be used in the release.

Android Platform

Get version name plugin

A important thing to show in the end of the release is the version name. It could be setted in the build.gradle of the project and will be shown to the final user in the Fabric Beta and Google Play.

The version name can be getted by the a fastlane plugin called get_version_name. So, save in a variable like this:

version = get_version_name

If it isn't installed yet (you can verify executing "fastlane actions gradle" in the terminal), you can install it by executing in the terminal

$ fastlane add_plugin get_version_name

Distribute by Crashlytics

If you don't know Crashlytics, you must be. If you do, let's go: fastlane helps you, with a simple syntax, distribute the .apk to specific emails and even specific group of emails predeterminate with its alias.

It's necessary put the api token and build_secret to link with your fabric.io account. These numbers can be found in

Settings -> Organizations -> API Key or Build Secret

Other important thing to do is set the apk path. Gradle had, in the fastlane context, a variable with this value:

lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH]

So the whole crashlytics action is:

crashlytics(
    api_token: "api_token_goes_here",
    build_secret: "build_secret_goes_here",
    groups: "group_alias_goes_here, group_alias_goes_here2",
    notifications: true,
    apk_path: lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH],
    notes: release_notes
)

Gradle tasks

The Clean gradle task is a good thing to execute before any build task to avoid unnecessary errors.

gradle(task: "clean")

It's easy generate the apk to release without any thing else to configure.

gradle(task: "assembleRelease")

But if you want add a specific flavor, this can be done:

gradle(
    task: "assemble",
    flavour: "Homol",
    build_type: "Release"
)

It can be possible replace the string Homol with your flavor else. Watch out with the first capitalized letter, even the flavor name in gradle were not capitalized.