Why Gretel?:
- Gretel can add system traces to multiple classes in one go, like all lifecycle callbacks in all Activities
- Gretel can add system traces to 3rd party code and generated code, like the Dagger code that manages the dependency injection
๐ง Gretel 0.2.0 Released
Gretel lets you instrument your android app by adding system traces during compile time. This release adds a DSL that allows you to target specific classes and methods that should be traced. Check it out here:
https://t.co/4jo22dBJPu
I'll be taking today at #dcldn22 about how we build the @StocardApp offline first. If you are curious how it works or if you want to see more raccoon pictures join me at 11:30 in Liskov ๐
I just arrived in London. Sadly I couldn't make it to the @droidconLondon speaker party tonight, but I'm looking forward to meet you all the next days at #dcldn22 ๐
๐ฃ Free #dcldn22 ticket giveaway!
I'm super excited to speak at @droidconLondon this year about how we build the @StocardApp offline first.
I have an extra ticket I want to share with the community. I'll pick a lucky winner in 24 hours. To enter just follow me and like
Andreas Wenger has been added to the #dcldn22 speaker lineup! @WengerAndi will discuss how his team built the Stocard Wallet #app offline first so that users could scan their loyalty cards or pay without any network connection.
Learn more here: https://t.co/oJwVN00dvB
Hey, @geekyouup, @ciarandowney Firebase Cloud Messaging is causing nearly 50% of the crashes we track for our app. We reported the issue 2 month ago but after a initial reply there is radio silence, could you have a look into it? https://t.co/Pch3Jr5ZN6
@pfmaggi In general I agree, but if we have different versions for different artifacts, shouldn't we also have different Changelogs? Or at least specifying for each release which artifacts it covers. Otherwise we won't know if a artifact was intentionally not updated or just forgotten
@pfmaggi I noticed that we are "encouraged" to update the play core library to 1.7.2. However the -ktx version only has 1.7.0 , the native one I only found with version 1.7.1 . Do we need to manage all 3 dependencies separately? The release notes still seem to cover all versions
@yigitboyar thanks! Checking the page again, I also noticed now that the Date of the Last Update is also correct already. Regarding the core-testing, this means that it is not intended to be in sync with the rest of the lifecycle libs (as the code sample suggest)?
@yigitboyar androidx.lifecycle should now be at 2.2.0, right? Only asking because the "Latest update" and the changes on https://t.co/7Bp0JPkBQS contradict each other. Also updating to 2.2.0 fails for me because androidx.arch.core:core-testing:2.2.0 seems to be not available yet.