How to diagnose white screen on startup on Android device

@rapropos thanks for that link. I hadn’t followed the above, (didn’t know about that) but have now. So now ionic serve runs fine, and if I build without the --prod flag it builds, but unfortunately as soon as I use the --prod I still get exactly the same error " build prod failed" as above. Perhaps there is something else I am missing. Perhaps the Ionic cli version? (I have 2.2.1).

I deleted my node_modules and did a fresh npm install, but didn’t make any difference.

Seems to be all about the NoOpAnimationDriver. There is a discussion on that here, so I tried adding the exclude test.ts and other option mentioned there…

"exclude": [
"node_modules",
"src/**/*.spec.ts",
"test.ts"
  ],
  "angularCompilerOptions": { "genDir": "i18n" },

…but unfortunately this hasn’t helped. My test.ts comes from installing everything mentioned in this tutorial, but perhaps this issue has nothing to do with my test.ts

The contents of the file animation_driver.d.ts mentioned in the error include

 /**
* @experimental
 */
 export declare abstract class AnimationDriver {
      static NOOP: AnimationDriver;
    abstract animate(element: any, startingStyles: AnimationStyles, keyframes: AnimationKeyframe[], duration:             number, delay: number, easing: string, previousPlayers?: AnimationPlayer[]): AnimationPlayer;

}

Something to do with the line static NOOP: AnimationDrive ?

Not sure what could be causing this. :worried:

My problem was actually with the test.ts, that had testbed stuff in it.I thought I had told TS to ignore it, but when I actually deleted it the problem suddenly went away. Wish I has tried that first (removing file by file until sorted it)

So, I now have it working with the following…

		 "dependencies": {
		"@angular/common": "2.4.8",
		"@angular/compiler": "2.4.8",
		"@angular/compiler-cli": "2.4.8",
		"@angular/core": "2.4.8",
		"@angular/forms": "2.4.8",
		"@angular/http": "2.4.8",
		"@angular/platform-browser": "2.4.8",
		"@angular/platform-browser-dynamic": "2.4.8",
		"@angular/platform-server": "2.4.8",
		"@ionic/storage": "2.0.0",
		"@types/c3": "^0.4.38",
		"@types/jszip": "0.0.32",
		"@types/lodash": "^4.14.51",
		"c3": "^0.4.11",
		"ionic-angular": "2.2.0",
		"ionic-native": "2.4.1",
		"ionicons": "3.0.0",
		"js-logger": "^1.3.0",
		"jslogger": "^1.0.3",
		"jszip": "^3.1.3",
		"lodash": "^4.17.4",
		"moment": "^2.17.1",
		"ng2-translate": "^5.0.0",
		"rxjs": "5.0.1",
		"semaphore-async-await": "^1.3.2",
		"sw-toolbox": "3.4.0",
		"zone.js": "0.7.2"
	  },

Yeah, you must aggressively exclude all test files in tsconfig.json. If ngc sees a single one of them, your build will blow up.