Some templates stop rendering after upgrade 3.6.3 -> 3.7.0

No server-side errors triggered. No client-side errors triggered. An empty template is rendered. Downgrading back to 3.6.3 solved the problem. Details below.

Template

<template name="layoutBlankPublic">
	{{> Template.dynamic template=content}}
</template>

FlowRouter

import { FlowRouter } from 'meteor/ostrio:flow-router-extra';
import { BlazeLayout } from 'meteor/kadira:blaze-layout'

const publicRoutes = FlowRouter.group({
	name: 'public'
});

publicRoutes.route('/login', {
    name: 'login',
    action: function () {
        BlazeLayout.render('layoutBlankPublic', { content: 'login' });
    }
});

Oddly enough, a different layout template DOES work?!

Template

<template name="defaultLayout">
{{#if loggingIn}}
	{{> loading}}
{{else}}
	{{#if authenticated}}
		<div id="wrapper">
			{{> authenticatedNavigation }}
			<div id="page-wrapper" class="gray-bg">
				{{> authenticatedNavbar }}
				{{> Template.dynamic template=content}}
				{{> footer }}
			</div>
		</div>
	{{else}}
        <div id="wrapper">
            <div id="page-wrapper" class="gray-bg">
                {{> publicNavigation }}
                <p>You are not authorized to view this page.</p>
                <p>Please <a href="/login">login</a> to view this page</p>
            </div>
        </div>
	{{/if}}
{{/if}}
</template>

FlowRouter

import { FlowRouter } from 'meteor/ostrio:flow-router-extra';
import { BlazeLayout } from 'meteor/kadira:blaze-layout'

FlowRouter.route( '/dashboard', {
	name: 'dashboard',
	action: function() {
		BlazeLayout.render( 'defaultLayout', { content: 'dashboard' } );
	}
});

[dr-dimitru]

@RomanBf two different Blaze-based rendering engines.

this.render features:

• Made with animation performance in mind and respect to requestAnimationFrame
• Pass and assign data and/or arguments directly to template
• It’s more “rendering engine” than “templating engine”
• Up do date, tested with latest Meteor and Blaze releases

BlazeLayout.render features:

• Described here, in official docs

[dr-dimitru]

@cormip @jankapunkt please check latest v3.7.1 release, this issue should be solved.

Feel free to reopen it in case if the issue is still persists on your end.