Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Commit

Permalink
Add lane to upload dSyms to Crashlytics
Browse files Browse the repository at this point in the history
  • Loading branch information
1nput0utput committed Mar 19, 2018
1 parent e1dbf7d commit d56c373
Show file tree
Hide file tree
Showing 2 changed files with 33 additions and 17 deletions.
38 changes: 21 additions & 17 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,33 +1,37 @@
## 0.5.0 (March 19, 2018)

* Added the lane `refresh_dsyms` to help upload dSyms to Crashlytics.

## 0.4.0 (July 25, 2017)

* Added the ability to pass `testflight_groups` parameter to the `publish_testflight` lane.

## 0.3.0 (July 4, 2017)

* The `prepare` lane now performs a `pod repo update` before doing the
`pod install` lane to avoid problem of an out of sync pods repository.
* The `prepare` lane now performs a `pod repo update` before doing the
`pod install` lane to avoid problem of an out of sync pods repository.

* Added a `bootstrap` lane used to setup the project which does, `prepare` and
`sync_certificates`.
* Added a `bootstrap` lane used to setup the project which does, `prepare` and
`sync_certificates`.

* Added possibility in `publish_crashlytics` and `publish_testflight` to pass
a custom version value (via `:version_number`).
* Added possibility in `publish_crashlytics` and `publish_testflight` to pass
a custom version value (via `:version_number`).

* Fixed `overlay_version` to correctly retrieve current version number.
* Fixed `overlay_version` to correctly retrieve current version number.

* Split lanes in two sets, a public set and a private one. This is artificial
but you should never rely on the private set in your project's Fastfile.
* Split lanes in two sets, a public set and a private one. This is artificial
but you should never rely on the private set in your project's Fastfile.

* Changed `increment_build_number` accepted options. Only valid option now is
`:strategy` and can be one of `:bitrise` or `:testflight`.
* Changed `increment_build_number` accepted options. Only valid option now is
`:strategy` and can be one of `:bitrise` or `:testflight`.

* Renamed `increment_build_number` to `increment_build_version`.
* Renamed `increment_build_number` to `increment_build_version`.

* Renamed build tasks:
* Lane `crashlytics_build` renamed to `publish_crashlytics`.
* Lane `beta_build` renamed to `publish_testflight`.
* Lane `release_build` renamed to `publish_itunes`.
* Renamed build tasks:
* Lane `crashlytics_build` renamed to `publish_crashlytics`.
* Lane `beta_build` renamed to `publish_testflight`.
* Lane `release_build` renamed to `publish_itunes`.

## 0.2.0 (April 6, 2017)

* Removed the need to have a clean environment for non-build tasks.
* Removed the need to have a clean environment for non-build tasks.
12 changes: 12 additions & 0 deletions Fastfile
Original file line number Diff line number Diff line change
Expand Up @@ -202,6 +202,18 @@ platform :ios do
!ENV['BITRISE_IO'].nil?
end

desc 'Downloads dSYM from iTuneConnect and upload them to Crashlytics.'
lane :refresh_dsyms do
if ENV['CRASHLYTICS_API_TOKEN'] || ENV['GOOGLE_SERVICES_INFO_PLIST_PATH']
UI.important 'Skipping dSYM upload because CRASHLYTICS_API_TOKEN or GOOGLE_SERVICES_INFO_PLIST_PATH is missing!'
return
end

download_dsyms
upload_symbols_to_crashlytics
clean_build_artifacts
end

################
# Success/Error:
################
Expand Down

0 comments on commit d56c373

Please sign in to comment.