by Brian Lynn, Sr. Product Marketing Manager
While the Peter Pan in all of us loves a good summer vacation, over at Crashlytics we’ve been working hard the last couple months to make sure that by the time those back to school ads start running, and all the sand is washed out of your hair, we’ll have tons of upgrades to show off to you, along with all the “true” stories about how we totally got into that P-Diddy party in the Hamptons that one time.
In July (while you were working on your tan) we enhanced our SDKs’ features, shipping even more robust crash reporting functionality and powerful processing capabilities. And in August (while you were nursing your sunburn) we took it one step further, improving even the finest details of our Android IDE plugins with a seamless user experience, as well as enhancing the flexibility of our Gradle plugin to support any custom builds!
Dazzling Experience for Intellij and Eclipse Plugins
We get it. When adding new libraries or plugins to development projects, you want to see how the change might affect your code and feel completely confident—like I-stood-up-on-my-paddleboard-on-the-first-try-confident. That’s why we created a new, slick UI for getting Crashlytics up and running with a preview screen that gives you even greater visibility into the code. But we didn’t stop there, we’ve made the UI extra responsive, with hover and pressed states on clickable links.
To keep your project folders streamlined, we moved all Crashlytics data caches to OS-dependent cache locations. This way, the caches are still there, and you can access them whenever you need to. As a bonus (think free tickets to that labor day destination wedding) we also fixed a critical issue for you here, if you weren't running your IDE with admin privileges.
Upgraded Support for Custom Builds in Gradle
Picture this: you arrive at your favorite beach, strut down the sand greeting friends, score the perfect spot near the snack shack, then drop and successfully unfurl your beach chair on the first try without the slightest hesitation. That’s the type of flawless experience we want you to have when using Crashlytics to build APKs, so we set out to improve the support for non-standard build configurations in our Gradle plugin. Because we automatically detect customizations from the gradle file directly, you don't need to add extra Crashlytics-specific configuration params!
Here’s our internal changelog:
- Fixed non-critical bugs.
- Solved build processing and graphics related bugs.
Android IDE Tools
- Added a prompt for users with an expired token to re-login.
- Greatly improved the runtime performance of the plugin updater.
- Fixed a bug that can cause updates to fail in rare circumstances.
- Deployed a new WWW architecture based on modules allowing the client to request only the code required for that specific page. This should make page loads much, much faster.
We hope these updates make developing out-of-this-world apps, and the transition from summer to fall a bit easier on you. And as you pack away your miniature drink umbrellas and mentally prepare for pumpkin flavored beer you can now proudly add another Crashlytics blog post to your summer reading list. Don’t worry, we won’t tell anyone you didn’t get all the way through Infinite Jest like you had planned ;)