I found this and dug deeper before finding this thread, so here comes a few details.
0- This has rendered my application unusable for everything bellow Android 4.4, as it can’t transition states anymore (so it’s the most breaking change I’ve seen so far).
0.5- Testing a new app created from the sidemenu or tabs templates from Ionic doesn’t have this issue on either versions, which show there’s something else on slighly more complex applications that trigger this faulty behaviour.
1- That CALL_NON_FUNCTION pointer, along with the line the TypeError actually points to are wrong, as they actually point to where the console.log was called to log this error. The real error comes from ionic.bundle.js:20688:13 (on the OP case, that is). This confusion happened for me on Android 4.0.2 but didn’t on Android 4.3.
2- The error comes from the new $$RAFProvider (deals with monkey patching requestAnimationFrame) added on Angular.js v1.2.13 IIRC. They’ve patched it for Safari and old versions of Firefox on the following versions, but it seems that some browsers have requestAnimationFrame but not cancelAnimationFrame available, or the monkey patching from angular is bad.
3- To sum it up: cancelAnimationFrame is undefined, but requestAnimationFrame isn’t.