iOS 8 Compatibility

Fri Oct 10, 2014 10:31 am

Maryna,

I wish I could.... I'm using a 3rd party SaaS called Bugsnag that logs JavaScript errors that I don't trap myself. I check the logs from time to time, and after my latest upgrade of Oct 1st, I noticed these specific bugs started to emerge, bugs that I had never seen before.

As far as I can judge, they indicate failure to load resources, so the code that references these resources (Appery functions) fails and the error fires.

I think that some of Appery's core JS code is prone to such errors because it runs as soon as it loads, assuming that other resources have loaded. For example, appery.js is an IIFE (Immediately invoked Function Expression) taking jQuery as argument, assuming that jQuery is loaded! There's no guarantee that resources load in any particular order.

There are no edited source files in my project (except my own JS of course...)

Benny

Fri Oct 10, 2014 2:14 pm

[quote:]There's no guarantee that resources load in any particular order[/quote] they are loaded according to order in html file. Thus jQuery is loaded before appery.js

Sorry, we are not familiar with Bugsnag and it's accuracy...

Does the app work when you test it? Any errors in console?

Mon Oct 13, 2014 8:12 am

No, in lab conditions I don't come across these errors. Maybe under slow connection conditions errors actually happen. I understand your suspicion of unfamiliar Bugsnag, although my tests with this service showed that it does its job simply and reliably.

I hope that Appery's roadmap includes built-in minify/combine option. It should eliminate the potential timing problems.

Meanwhile, I look forward to maintenance releases that deal with iOS 8 effects.

Thanks, Benny

Mon Oct 13, 2014 2:29 pm

Hi Benny. The Bugsnag service looks really helpful - thanks. Question: I know that Appery is creating a mechanism for adding metadata without altering source code - -

https://getsatisfaction.com/apperyio/....

In order to install Bugsnag before that's done, is it correct for me to presume I would need to change source code?

Mon Oct 13, 2014 3:21 pm

Robert, this is maybe the biggest shortcoming of Appery. Once you touch the code you're dead as far as GUI is concerned That in my opinion renders their GUI unusable, b/c app life cycle never ends, and we always iterate and change our markup.

What I do is avoid Appery's GUI nearly completely, and build my markup in an external html file that I load async. There are great templating engines that help you do it. I'm using the one bundled with Underscore. Appery's core code includes Underscore so that's good.

So, I have my [very thin] startScreen.html outside Appery, with link referring to Bugsnag inside, and I manually update it when I need to.

Mon Oct 13, 2014 3:36 pm

Thanks Benny - given my skill level and reliance/comfort with the GUI, I was kind of afraid of that. Hopefully Appery's metadata-injection feature will solve my issues.

Mon Oct 13, 2014 3:43 pm

I agree. Appery is attractive to users from beginner level [and up], who need the GUI IDE. To their defense I can say that two-way editor is tough to build. However, allowing limited custom markup, say in the <head> tag content could be a reasonable compromise and a step forward.