BTService first tick happens earlier than activation
If you use a simple BT service (see bottom of this post), you can clearly see that its first tick will happen before activation. I consider this behavior a bug because it works against common sense, which assumes [Activation -> Tick, Tick, Tick -> Deactivation] instead of [Tick -> Activation -> Tick, Tick, Tick -> Deactivation] lifecycle. Activation is commonly used to set up various variables that are later used in ticks. With current behavior, user has to explicitly guard Tick with an artificial "have we activated yet?" check.
Answering to myself, this bug should be fixed by following commit:
answered Feb 18 '15 at 01:55 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here