![]() In my case it also takes a long time, so if it’s just to test the css I can just execute without prod:Ībout chrome://inspect/#devices, you can just type it in chrome to see and inspect your device, when you plug it with usb. ![]() Your app takes 20min to be built using the -prod flag, I presume: In most cases it works the way i intended so I don’t need to rebuild. ![]() I haven’t seen a significant difference between the browser and the device (except in some cases regarding flexbox in Android 4.4 and some special characters displayed differently).Īfter I check that it’s fine in the browser, I check in the device. Now i run (ionic cordova run android -livereload) and all urls seem to work properly. ![]() It seems that Cordova plugins have been updated somehow. Android: However, for ionic cordova run android -l or ionic cordova run android -l -address0.0.0. I have an app with more than 100 components and most of the time I test css/themes in the browser. System: Android SDK Tools : 26.1.1 (C:\Users\themhz\AppData\Local\Android\Sdk) NodeJS : v8.11.1 (C:\Program Files odejs ode.exe) npm : 6.0.0. So you could try to make your app work this way, it would be easier to test. Does your page that has the css applied need cordova to be shown? I use cordova to access native functionality, so if it’s just to see the page, I try to make the page content be displayed even without cordova (the page will be shown, even if I can’t execute some actions in the page). To use Cordova for this process instead, use the -no-native-run option. Finally, the native-run utility is used to run your app on a device. Then, cordova build is used to compile and prepare your app. Quite funny, since adding that parameter, let me run my App in the iOS debugger respectively in case of iOS was a must. Removing -address localhost from the command solve my problem means following command is ok. ionic run android -c -s -l -address localhost. If this time is like the dozens of other times I’ve encountered this, I will come back later tonight or in the morning and things will just be working again… No indication of anything useful in server or console logs… It has really made working in this environment very challenging when dealing with deadlines and scheduled deliverables as I’ve randomly lost hours of development time randomly without warn or reason due to this issue.Įdit: Like now… 30+ mins dead in the water and the moment I click save on this post (on another PC), the black screen is magically replaced with my app’s screens without any intervention from me (other then sending mental deathrays at it).I see that you posted an error when running ionic serve. This command will first use ionic build to build web assets (or ionic serve with the -livereload option). I found the solution, I was running the command. Out of the blue, I start getting the black screen on the device after saving a few simple CSS changes… I can kill every node.exe instance, I can uninstall and reinstall the app, I can reboot my PC and tablet - all to no avail… I have start a project with this: nvm install 10.16.3 nvm use 10.16.3 npm install -g ionic npm install -g cordova ionic start myApp tabs -cordova cd myApp ionic cordova run android -livereload Without -livereload the app works: But wi. I’ve been working in this app all day without so much as the first issue. Like now… Why I am replying to this thread is because the black screen issue began randomly again and so I again went looking for info on how to resolve it… Just as you’ve described, I can run without livereload using this exact codebase without any issues… Press Win+R, run 'WF.msc', add 'C:Program Filesnodejsnode. It’s actually quite infuriating, as it seems to begin randomly and end just as randomly… 1 Answer Sorted by: 0 You may check your firewall setting, add 'node.exe' to excluded program. I can't use the command ionic run android -livereload as described in the doc here because it synchronizes the www folder where (after a gulp build) I have the minified files and not the source files. Commands: 1) ionic serve - Serves to localhost:8100 and I can see the app in Chrome. Now after the update to Capacitor Version 3 I cant use Live Reload in my Ionic Angular Project anymore. This means that to run the project in the browser I use gulp serve and to run in the Android device I use gulp build & ionic run android. In the folder resorces/android/xml there is a file networksecurityconfig. I enabled port 8100 in firewall (also turned off firewall completely) so when I open Chrome on the Android device and navigate to 192.168.51.28:8100 I can see the app. Over the past week I have been running ionic serve -device -l to test on my Android L device with live reload. I also have this issue sometimes, though I’ve yet to put my finger on what actually brings it about… This is because the clear text is not allowed. Hey guys, I have searched around the forums, but couldn’t find anything that described my issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |