Error upgrading beta.4 -> beta.5
See original GitHub issueI am experiencing an error in the browser console after upgrading from beta.4 to beta.5. AFAIK there are no breaking changes in the code. The error message doesn’t give me much information; maybe somebody knows what’s going on.
The error message is the same in development and production mode. No error output during compilation.
Browser error (preventing the application to bootstrap):
ERROR Error: Uncaught (in promise): TypeError: Object(...) is not a function
TypeError: Object(...) is not a function
at app.0579d7e8ad84bee767ca.bundle.js:54
at e.invoke (polyfills.b381d02f20eaa4d78933.bundle.js:8)
at o.run (polyfills.b381d02f20eaa4d78933.bundle.js:8)
at t.runOutsideAngular (app.0579d7e8ad84bee767ca.bundle.js:433)
at new t (app.0579d7e8ad84bee767ca.bundle.js:54)
at factory (app.0579d7e8ad84bee767ca.bundle.js:54)
at app.0579d7e8ad84bee767ca.bundle.js:621
at No (app.0579d7e8ad84bee767ca.bundle.js:621)
at Mo (app.0579d7e8ad84bee767ca.bundle.js:621)
at t.get (app.0579d7e8ad84bee767ca.bundle.js:636)
at app.0579d7e8ad84bee767ca.bundle.js:54
at e.invoke (polyfills.b381d02f20eaa4d78933.bundle.js:8)
at o.run (polyfills.b381d02f20eaa4d78933.bundle.js:8)
at t.runOutsideAngular (app.0579d7e8ad84bee767ca.bundle.js:433)
at new t (app.0579d7e8ad84bee767ca.bundle.js:54)
at factory (app.0579d7e8ad84bee767ca.bundle.js:54)
at app.0579d7e8ad84bee767ca.bundle.js:621
at No (app.0579d7e8ad84bee767ca.bundle.js:621)
at Mo (app.0579d7e8ad84bee767ca.bundle.js:621)
at t.get (app.0579d7e8ad84bee767ca.bundle.js:636)
at E (polyfills.b381d02f20eaa4d78933.bundle.js:15)
at E (polyfills.b381d02f20eaa4d78933.bundle.js:15)
at polyfills.b381d02f20eaa4d78933.bundle.js:15
at e.invokeTask (polyfills.b381d02f20eaa4d78933.bundle.js:8)
at Object.onInvokeTask (app.0579d7e8ad84bee767ca.bundle.js:433)
at e.invokeTask (polyfills.b381d02f20eaa4d78933.bundle.js:8)
at o.runTask (polyfills.b381d02f20eaa4d78933.bundle.js:8)
at p (polyfills.b381d02f20eaa4d78933.bundle.js:8)
at <anonymous>
Versions:
- Angular 6.0.0-beta.8
- Material/CDK 6.0.0-beta.5
- Typescript: 2.7.2
- RxJS: 5.5.7
- Webpack: 4.2.0
No dependencies have been modified going from Material beta4->beta5
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Beta 4 failed to update to beta 5 | MacRumors Forums
Tried 3x on a Mac Studio with the beta 4 running on a Thunderbolt 3 SSD. It downloaded, attempted install, booted into phase...
Read more >Ventura beta 4 fails to update to … | Apple Developer Forums
Ventura Beta 4 is not updating to Beta 5 on a Mac Studio booting Ventura from an external Thunderbolt SSD. Previous updates worked....
Read more >Beta 4 > Beta 5 Upgrade - Fatal Error | XenForo community
Hi, While uploading upgrade package I'm getting Fatal error on the forums: Fatal error: Call to undefined method XenForo_Session::startPublicSession() in...
Read more >Error Upgrading from ASP.NET 5 Beta 4 to Beta 5
I have followed the steps here to upgrade from ASP.NET 5 Beta 4 to Beta 5 but am getting an error at runtime...
Read more >phpBB • PHPBB3 BETA 4 - BETA 5 UPGRADE PROBLEM
PHPBB3 BETA 4 - BETA 5 UPGRADE PROBLEM ... Hi, I recently did an upgrade install of phpbb3 b4 to phpbb3 b5 ever...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@julianobrasil @josephperrott
Thanks guys, I’ll give it a shot. Maybe I’m stupid but I couldn’t find this in the changelog breaking changes, so I suspect I’m not going to be the only one struggling to upgrade.
A suggestion could be to add this as a requirement for the update. Thanks again guys, appreciate the feedback. Honestly I’d never have thought of it as I didn’t want to complicate bugfixing by upgrading both Angular, RxJS and Material at the same time 😃
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.