0
Fixed

License check failure prevents alarms from working

Hector Martin (marcan) 4 years ago • updated by Jona (Lead Developer) 3 years ago 9
I've been using XiiaLive as my alarm clock, which is usually quite reliable. Today, though, it didn't work, and I found out that XiiaLive was complaining that the license check failed.

I understand that Google Play license checks may rarely malfunction, but would it be possible to at least allow basic alarm functionality to work even if it does? Perhaps just fall back to the default alarm ringtone in that case, just as it would if stream playback fails. Having the alarm fail to work due to a licensing check is quite frustrating, and I don't want to have to set up a back-up alarm in another app and deal with disabling it every time just to work around this potential failure mode.

I've been using XiiaLive for over a year now, and I've only had it fail to wake me up twice; the other time there was no audio output, but that may have been a device snafu (a reboot cleared it up).

Answer

Answer
Fixed

Hey the mentioned issue should be resolved. If for some reason you are still having issues please let us know.

Planned
Thanks for the feedback. I'm also seeing other users reporting licensing check failures. Could you provide the number shown when you see the licensing check failure message?

I been looking into this last week and couldn't determine the cause and thought it might just be GooglePlay going through some patch or bug. I'll keep looking into it. Sorry for the inconvenience.
Unfortunately, when I saw the message in my half-asleep state I didn't think to take a screenshot, and I haven't seen it since. It seems it was a transient failure. If it happens again I will make sure to note down the number.

My request was more of a general safety feature to allow alarms to work (perhaps in a dumb/non-streaming mode) even if the license check fails though; this should be independent from the actual cause of the license failure.
Yeah, I understand the issue. The licensing check is very relaxed and on failure it doesn't complain right away it keeps trying for days.

What device do you have and what version of Android is it running? Android 5.x seems to be having some issues with licensing problems.
This is a Nexus 5, and I have indeed recently upgraded to 5.x (CyanogenMod 12, previously 11), so that matches up.

Edit: 5.0.2 specifically - the 20150219 nightly of CM12.
Today it happened again, and I caught it. When the alarm triggered, the stream started and started fading in as configured. A few seconds later, though, it abruptly stopped (with a very brief jump to full-volume as it did so - this tends to happen when I stop the stream manually too) and the message appeared. Error code -46767.
Cool! Thanks for the info. Ok that confirms the issue and I have already fixed it. I'm shooting for an update today.
Answer
Fixed

Hey the mentioned issue should be resolved. If for some reason you are still having issues please let us know.