AutoWear AutoWear: Callable returned a null value

Discussion in 'AutoApps' started by FourQ, Sep 17, 2020.

  1. FourQ

    FourQ New Member

    Dec 12, 2015
    Likes Received:

    Is anyone having problems with AutoWear? I really do rely on it but I keep getting
    'The callable returned a null value'.

    Checking heart rate, battery level, AW apps, floating icons and even shake detection all trigger the error message. Basically, every WearState event.
    Because it's used so much the toast message is on the screen nearly all the time, to the point where other toasts are massively delayed, often minutes after triggering. Using the Turn Off action no longer works properly because putting the phone down means moving my wrist so the Callable error turns the screen on again.

    I can't remember making any changes to Tasker to break anything overnight and every change to AutoWear is done within Tasker.

    Please help. Thank you.

Share This Page