I found this issue that is absolutely imposible to debug for me. It happens like every other time so it's not clearly repeatable. As soon as I hook my iPad into remote debugging the issue disappears completely.

It seems to happen after a certain point of template complexity and nesting level. This can cause that the name attribute in invokeAmbiguous is "undefined". This of course crashes at the next call setupHelpers. Any idea what circumstances have to occur to have an outcome like that? I've already checked that the context and the template is fine.

One of the possible templates where this can happen is:

<ul>
  {{#each filters}}
    <li>{{this}}</li>
  {{/each}}
</ul>

Where the context is

{
  filters: [
    "Transfer Inklusive"
  ]
}

There seems to be a Problem with {{this}} and it happens on the template call.

First we thought that splitting the heavy nested stuff in Partials would fix the problem. But after a few hours it started again. We do not precompile our templates in node.js.

As I said - it's almost impossible to reproduce and to debug because it only happens in IOS Safari when it's not hooked to a debugging device like every other reload. Could it possible be a race condition or some memory issues?

EDIT: Stack Trace:

'undefined' is not an object

[email protected]:1727
[email protected]?0:1735
[email protected]?0:1569
[email protected]?0:1190
[email protected]?0:1842
@handlebars.js?0:1850