There's not a whole bunch of machinery in BK's annotation processor, after all

@jw: When I clean the project it regenerates fine in the test project I made. But If I do the same thing in my main project it still does not generate the binding for my view.

I do think its something with kapt however. I’ve been having similar issues with Realm annotations not getting noticed after making modifications.

is sourceset merging for productflavors possible with kotlin? (ie: overriding a class implementation based on product flavor)

@jw: the workaround seems to be renaming the variable, cleaning and rebuilding. If I don’t rename the variable it won’t generate it correctly even after a clean.

Exist any good way to do unit test of api call made with retrofit?

There is no way to unit test API calls from client. That would be something between integration and e2e tests. What I do in unit tests is providing stubs for interfaces, e.g. when I need to combine multiple calls and map the data before passing it to UI.

swap the retrofit-implemented instance for a simple class that implements the API interface

Ok

Thx.

@jw: I have in my head the idea that you shouldn’t try to call

getResources()

on the context until after

onCreate()

has run but I can’t find any doc about that. Does that ring any bell? Am I imagining things?

The base context is almost immediately attached right after the constructor, if I remember correctly. So you should be able to call it at any point that your code would be able to even get access to a reference of Application or Activity.

I just tested it in an anonymous initializer; it threw an NPE

We’re seeing occasional cases where resources are null, which would tend to point that even though the context is attached, resources are not created yet

Trying to justify my hunch with some doc but coming up empty so far, so diving into AOSP

maybe http://b.android.com/56296

@damian: hah. well that's not fair!

true simple smile

@damian: Ok that confirms my thought. Now I wonder if you can access it in the middle of

onCreate()

. I suspect you’ll get the NPE if you try before

super.onCreate()

and that it would work if after. Speculating right now, haven’t tested

even before

super.onCreate()

you should be fine

attach is called about 15 lines up from calling onCreate: https://android.googlesource.com/platform/frameworks/base/+/refs/heads/master/core/java/android/app/ActivityThread.java#2320

I just tried before

super.onCreate()

and it was good to go 👍 (I happen to have the debugger open right now 😉 )

But when it is attached, does it have a non-null

getResources()

?

I have a hunch that might be done later but no evidence to back that up so far

for

Fragment

? haven't tried

for "attaching" an activity, looks like

onAttachedToWindow

is called after

onCreate

quick test with the debugger shows that

resources

is non-non even before

super.onAttach

in `Fragment`s

(this is all with support `Fragment`s and

AppCompatActivity

fwiw)

The crashes we’re seeing seem to come from broadcast intents, so not

ApplicationContext

whatever the context is in those situations