Angular 2.0 router navigation not working on iOS WKWebView
<p>Because of some performance issues, I'm trying to upgrade an angularJS2/phonegap app to use WKWebView on  iOS. </p>

<p>Unfortunately, any calls to route navigate do not work.  This includes <code>routerlink</code> and <code>this.route.navigate</code> calls. There are no errors being thrown.  Has anyone else seen this and/or perhaps have a workaround?  </p>

<p>The code works fine using the normal UIWebView.  </p>

<p>I'm a relative newbie to Angular so any suggestions are welcomed.</p>

<p>Here's what some of the relevant code looks like:</p>

<pre><code>import { Component } from "@angular/core";
import { Routes, Router, ActivatedRoute } from "@angular/router";
import { LoggedInCallback } from "./service/cognito.service";

export class HomeComponent implements LoggedInCallback {

constructor(public router:Router){
}

isLoggedIn(message:string, isLoggedIn:boolean) {
    if (isLoggedIn){
      this.router.navigate(['/home/cl']);
    }
    else {
      console.log('HomeComponent: '+message);
    }
}
</code></pre>

<p>routing module:</p>

<pre><code>import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { FormsModule } from '@angular/forms';
import { Routes, RouterModule } from '@angular/router';
import { CategoryListComponent } from './categorylist/categorylist.component';


const approutes: Routes = [
    {
         path: 'home/cl',
         component: CategoryListComponent
    },
    ...
];
@NgModule({
  declarations: [

 ],
  imports: [RouterModule.forRoot(approutes), 
        BrowserModule, 
        FormsModule],
  exports: [RouterModule]

})
export class AppRoutingModule { }
</code></pre>

<p>In response to a comment below:</p>

<p>As mentioned, this a phonegap app, so most of the references are using (I assume) the file: protocol.  However, the first page loads okay, and it references content within a single JavaScript file. The odd thing is that all of the other router-referenced content are also in that same JavaScript file. </p>

<p>I was hoping that someone would understand the nuts and bolts of the router behavior to explain why it doesn't work in this environment.</p>