-
Notifications
You must be signed in to change notification settings - Fork 666
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ionic 4] "(intermediate value).fill is not a function" #3709
Comments
Quick update: I am facing the same problem on Windows10, too. |
I'm facing roughly this same issue. Embedding an angular-based website in a WebView on an android emulator, and loading it on the emulator results in the identical error. It's not whitescreened because I load a default loading spinner in the html prior to |
I'm facing the same issue, anyone have any clues what could be causing this? |
I was able to get around this (note: I was not using ionic, but was using angular which I understand ionic uses behind the scenes) by manually adding in the Traceur dependency, which Angular 2 has as a bug. (see angular/angular#3694) The specific line I added can be found here: https://stackoverflow.com/questions/32382549/typeerror-array-from-is-not-a-function/32383485#32383485 Not sure if that'll fix your issues, but it helped in fixing mine. |
weird... just got this same error when trying to emulate on android, worked fine on iOS and browser. gonna try to troubleshoot a bit, in the mean time did anyone find the cause on their side?im not sure why the Traceur dependency would fix it, but I'll try that as a last ditch effort if I dont find anything else. |
Just a small update. I've tried starting a new tabs project via the Ionic CLI. Added capacitor. Deployed it via Android Studio, but I'm still getting the exact same error. (I said I would investigate just in case, it wouldn't be something causing this from my app) In any case, the error seems to be originating from Angular core. Any ideas / suggestions on how to fix this? |
Also tested with Cordova, and getting the white screen (new tabs generated project) - so possibly the same error as with Capacitor. Ionic: ionic (Ionic CLI) : 4.7.1 (/usr/local/lib/node_modules/ionic) Cordova: cordova (Cordova CLI) : 8.1.2 (cordova-lib@8.1.1) System: NodeJS : v10.1.0 (/usr/local/Cellar/node/10.1.0/bin/node) |
me too. |
Yes, just tested and Ionic 3 works. Issue only on Ionic 4. Although Ionic 3 uses "@angular/core": "5.2.11", whilst Ionic 4 uses "@angular/core": "~7.1.4". And it seems that the error is originating from the angular core package based on my screenshot from above (when testing with Capacitor). |
Does anyone solve the problem? |
@ruslan-bikkinin @PLorand |
@zuohuadong do you mean https://github.com/ionic-team/cordova-plugin-ionic-webview? I updated ionic cli and recreated application yesterday and the problem is still persist, but only on emulator. |
https://play.google.com/store/apps/details?id=com.google.android.webview You can update it. The default webview version of the system is 44 . |
I'm facing the same issue, any solution? |
Not yet on my side... Maybe someone else found a solution and can provide a guide to it?!.. But what I'm thinking of, shouldn't this be braking for more people, or there is nobody (only a few) people using this version of Ionic 4? Seems a bit bizarre, if you ask me. |
I think you can uncomment the polyfills from However, after a couple of tests, i think ionic v4 has issues with custom styles on older versions of webview (maybe because of css variables?) |
I have just tested with the latest release of Ionic (4.0) and the same problem persists. It's a "blank" project setup with CLI 4.9.0 with Cordova integration. Blank white screen in Android Simulator. Didn't have time yet to test on a phone. Ionic: ionic (Ionic CLI) : 4.9.0 (/usr/local/lib/node_modules/ionic) Cordova: cordova (Cordova CLI) : 8.1.2 (cordova-lib@8.1.1) System: NodeJS : v10.1.0 (/usr/local/Cellar/node/10.1.0/bin/node) |
Hey folks! @ruslan-bikkinin, what android version have you tested on? Is this android simulator only? This sound a lot like ionic-team/ionic-framework#15438, which is a multipart issue.
|
Uncommenting the polyfills actually solved the issue in the simulator. I will also test later with an actual device. This is was persisting both on the simulator as well as the real device. Device running Android 6.0.1 Thanks for the help @mhartington ! |
Hi @mhartington I test it on Android 6, issue persists only on emulator |
Real devices come with system webview up to date, right? Emulators have the "initial" webview version, that's why it's outdated. |
Yes, a real device with have the updated webview. Emulators have older webviews. I would even suggest using a real device over emulator in some cases. Closing this as it is not a CLI issue. |
@simion You have no control of the web view on a users device. I've run into issues with not having these polyfills for users with older chrome versions on android phones. Probably best practice to enable these pollyfills and support chrome back to version 40 or so. |
I will say that this will become easier in the next version of the angular-cli. It will support differential loading and load the polyfills automatically |
Description:
I am trying to debug basic tabs ionic4 project running on android emulator and I get white screen in app in emulator and
(intermediate value).fill is not a function
in Console tab of Chrome Dev Tools after inspecting it in Chrome. I tested it on Windows 10, Ubuntu 16 and Mac High Sierra and on each OS I got white screen, but only on Ubuntu, additionally, I got an error in Console tab. As far as I know, white screen appearance is a known issue for Ionic 4 apps, but I didn't find any mentions of errors during debugging it.Steps to Reproduce:
ionic cordova platform add android
ionic cordova emulate android
chrome://inspect/#devices
inspect
Output:
Output of ionic cordova emulate android --verbose
My
ionic info
:Other Information:
Please, let me know if you need something more to identify the cause of the problem.
The text was updated successfully, but these errors were encountered: