https://github.com/autonomousapps/crashlytics-kdsl-issue
Reproducer for issue with Crashlytics and Kotlin DSL
https://github.com/autonomousapps/crashlytics-kdsl-issue
Last synced: 2 months ago
JSON representation
Reproducer for issue with Crashlytics and Kotlin DSL
- Host: GitHub
- URL: https://github.com/autonomousapps/crashlytics-kdsl-issue
- Owner: autonomousapps
- Created: 2019-02-12T22:28:56.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2019-02-12T22:44:05.000Z (almost 7 years ago)
- Last Synced: 2024-12-28T15:29:49.019Z (about 1 year ago)
- Language: Kotlin
- Size: 124 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Crashlytics-KDSL-Issue
Reproducer for issue with Crashlytics and Kotlin DSL
The issue was originally described [here](https://stackoverflow.com/questions/53233826/android-and-the-fabric-crashlytics-plugin-always-generates-a-uuid-gradle-kotl), along with a workaround.
To verify that this works as expected with the Groovy DSL, checkout commit with ID **c3d3c5b**, run `./gradlew assembleDebug && ./gradlew assembleDebug`, and observe the output:
> 27 actionable tasks: 27 up-to-date
which indicates every task was up to date and none had to re-run.
To verify the issue with the Kotlin DSL, checkout **master** (or commit ID **00a532c**) and do the same thing. Observe the output
> 27 actionable tasks: 4 executed, 23 up-to-date
which indicates 4 tasks were re-run. You may furthermore navigate to the [build scan](https://scans.gradle.com/s/rbjvtykf2gmks/timeline?task=mvjiy2pq57wvg) and observe that the `:app:fabricGenerateResourcesDebug` task re-ran.