Cordova and different iOS versions.

[abarax]

I have set up my transition map and am using {{liquid-outlet}}. Everything is working perfectly in Firefox/Safari/Chrome on the desktop.

When I build the app with cordova and deploy to an iOS device, the transitions seem to only work on iOS 8 and not on iOS 7. On iOS 7 it acts as if liquid-fire was never installed and its just a regular outlet. On iOS 8 it works like a charm.

I have other CSS animations that work on iOS 7 that have been set up manually using the transition property.

Any ideas as to why this might be happening? All I can think is that the particular types of animation, that liquid-fire are using, arn't supported by iOS 7's version of webkit they use with webview. But then why are regular transitions working?

[ef4]

First thought, there may be exceptions that are being swallowed by this bug: tildeio/rsvp.js#278

Unfortunately, I don't think the fix has hit an ember release yet. You can work around it in this case by patching liquid-fire like this:

diff --git a/app-addon/views/liquid-outlet.js b/app-addon/views/liquid-outlet.js
index ddbac07..cc05a26 100644
--- a/app-addon/views/liquid-outlet.js
+++ b/app-addon/views/liquid-outlet.js
@@ -48,7 +48,7 @@ export default Ember.ContainerView.extend(Ember._Metamorph, {
     }

     this._runningTransition = transition;
-    transition.run();
+    transition.run().catch(function(err){console.log(err); throw err;});
   }).on('init'),

   _liquidChildFor: function(content) {

(liquid-fire deliberately soldiers on if there are exceptions during a transition, degrading to "normal outlet" behavior. The errors should get reported by Ember's default error handler, but don't currently due to that RSVP bug.)

I would check that first and see if it turns up something useful.

[abarax]

Ok, great idea. I'll try that now.

[abarax]

OK a bit more digging, using the patch you suggested, uncovered this: "Can't find variable: Promise"

This is because iOS7 does not support Promises but iOS 8 does!

The good news is that it has been fixed by this e95b69b commit (1 day ago!)

Thanks for the help, open source is fun!

[ef4]

Thanks, glad it worked out.

I'm going to build a warning like that patch into the library itself, before it snags somebody else.