I would like to get serious in using Kotlin for my android development. But how? I heard of a suggestion: let say you have gradle flavors&build types similar to

u2020

: - keep for now the production code

src/main

and

src/production

in pure java - use Kotlin in build variants

src/internalDebug

, `src/test`and

src/androidTestInternal

What do you think of this strategy? Has anyone started to do something like that?

@jmfayard: why you do not wont to use Kotlin on production?

not all my coworkers know kotlin, it's not 1.0 yet, the boss has not approved it yet.

bosses 😞 1. yours coworkers will see kotlin anyway in test etc. so they have to know kotlin as good as it would be on production 2. If I ware you I would try to come your boss around to use kotlin. Maybo some presentations, internal workshops? I am using Kotlin in 3 production apps and one lib:) Anyway your idea may works:) unit test in java and junit is a nightmare and in kotlin its looks pretty nice. What would you like to place in 'internalDebug' ? mocks/stubs etc?

I’d suggest starting with internal workshops and then implementing tests with Kotlin

@jmfayard: I would suggest setting up a kotlin branch instead and selectively move some classes to kotlin, then you can use that branch for internal testing and the normal master for production. Saves a lot on the "how can I get this to work with gradle" dance.

it's what I did for my app. The kotlin branch then was promoted to master fairly quickly simple smile

@jmfayard: Your concerns about variants are orthogonal with Kotlin

Also in my experience, it’s rare to need

internalDebug

, most of the time, an

internal

and a

debug

directories are enough. I think

u2020

uses those probably more as a showcase. They also have variant-specific dependencies, which are also rare in my experience

In my experience, the opposite of what he said is true

There's nothing showcase-y about u2020. We have the same setup internally for our apps.

I don’t doubt it, I still think it’s uncommon

It's not meant to be common. It's meant to demonstrate a non-trivial setup.

Common is boring, bad, and inhibiting

Words to live by

Has anybody seen a reason why Android extensions would call

findViewById

on every access in a custom view? Looking at the bytecode viewer, the cache isn't used at all.

hey, has anyone successfully used LeakCanary with a Kotlin app?

i am trying it with mine, but LeakCanary bites it when it comes to actually showing me the leak it thinks it found.

apparently LC doesn't like Android 6.0 though, so i'm trying to deduce if it's that or Kotlin that's making LeakCanary angry

LeakCanary with M won’t work at all, so if you’re seeing issues on M that is probably it. I’ve been able to use it on <M devices without issue.

i've read that they fixed the M issue in 1.4, but i am having a hell of a time finding a way to try that out

add the sonatype snapshot repo to your repositories, update versions to 1.4-SNAPSHOT

hm, i couldn't find the sonatype url; google reveals it was in changelog.md all along

embarrassing

I’m having an issue with ButterKnife and Kotlin. It’s unable to bind just one of my views in my activity. However, if I use find it works correctly. When I look in the kapt generated file I see that it’s missing the view that is not being bound. Anybody else seeing this?

I’m seeing this now on two different files, one an Activity and one a Fragment.

Can you whittle it down to a small test case?

Yeah, I can try. The odd thing is it works for other views fine. In one case its failing for a ProgressBar in an Activity and another is a RecyclerView in a fragment.

@jw: I created a test project. On the first build it generated everything correctly. Once I added another view it did not create the binding in the generated file.

May be a kapt bug, not necessarily BK