I'm working on ionic2.Few days ago,ionic2 was updated.After splash screen,we get the white screen for 14-15 second ,due to ionic2 was updated.
Add the --prod flag during any of the following CLI commands:
// If iOS
ionic emulate ios --prod
ionic build ios --prod
ionic run ios --prod
// If Android
ionic emulate android --prod
ionic build android --prod
ionic run android --prod
More about this.
there is some issues with that, you can follow them here github.com/driftyco/ionic/issues/9686 there is also some issue in ionic-app-scripts and there is some solutions try it
I'm assuming this in Android specific. I was having the same problem, the issue is two-fold:
The app is loading very slowly. If you watch console logs you'll see you get a note about it's taking 11000ms to load or whatever
Android is trying to be helpful by hiding the splash screen before you app is actually ready
I can't help you with #1, review your plugins, google around a bunch, and good luck. As for #2, you can add the line to config.xml to resolve
<preference name="AutoHideSplashScreen" value="false" />
Increase the SplashScreenDelay until you the app is reliably loaded before it hides.
Make sure you have SplashScreen.hide() in your platform.ready function in your main module as well so that when your app actually does load it'll hide.
You can find a bit more in Cordova, Android, incredibly slow loading
Related
I've developed a Flutter app but when I create its apk, it's run perfectly on first installation and after that I close my app and rerun then it is not showing any pages.
You might need to check the logs to see what is happening. Use Logcat extreme for checking the logs on your android device.
I recently completed my app in Flutter and I built a release APK. The Build APK is not working at any mobile and it is simply displaying as a White Screen. The debug APK in emulator was working fine while the release APK is not working. Can anyone help me out to solve this and Thank you soo much..!!
Did you sign your app correctly?
https://flutter.dev/docs/deployment/android
Try this to get more informations on what is happening:
flutter devices
flutter run -d [deviceID] --release
This will run the android app in release mode but you can still see logs
If your app requires internet permission, you need to make sure that it's specified. If not given it will still work on debug mode and not on release mode.
Android > App > Src > Main > AndroidManifest.xml
<uses-permission android:name="android.permission.INTERNET"/>
I'm developing an app using Baqend and ionic. When I run ionic serve the app runs fine in the browser and it is able to call Baqend. However, when I run ionic cordova emulate ios suddenly Baqend is not working in the Xcode emulator and it does not produce any errors in the console even with adding the --consolelog parameter.
I also tried:
Opening the project inside of Xcode and running it from there but same result.
Running the ionic/Baqend starter (https://github.com/baqend/ionic1-starter) and same result.
How can I debug this issue?
Update: I just tested it with Android using ionic cordova emulate android and it worked fine. So it seems that the issue only exist with ios.
The issue was solved by adding <allow-navigation href="https://*.app.baqend.com/*" /> in config.xml file.
I'm developing an ionic v2 app but even working on ionic lab it gets a complete white screen on the ionic view. If I do the same withe the ionic v1 it works.
ionic start sample --v2
cd sample
ionic lab
ionic upload
It shows white but
ionic start sample
cd sample
ionic lab
ionic upload
It works perfectly. No changes on the code at all
Thanks
ionic 2 needs at least 4.4 android to work, lost a lot of time on this and there is nothing on the ionic website informing about that. Writing down here to help anyone in the future.
Ionic v2 supports android 4.4 and up. The older browser on pre-4.4 devices do not have the features needed for ionic2 and angular 2 to work. Though this can be fixed with crosswalk.
The supported platforms are list here:
http://ionicframework.com/docs/overview/#browser-support
You can go back to 4.1 with crosswalk it states.
ionic 2 needs at least 4.4 android to work,.. for more info debug app in chrome.
from ionic 2 Ionic officially stops to use ionic lab.
You can run and test your app in browser using command "ionic serve".
Ionic2 app was initially created with --v2 flag but now they removed it . So nothing happens with --v2
Better way to solve the code 1st time by running directly into android devices by
Ionic cordova run android or
Ionic run android
Then connect your device with your system and open chrome and enter chrome://inspect to the url
Now you can console log the the error and can find the way of solutions.
Now try to run by ionic view
Remove the platform and then add it again.
please try eionic start sample --type=ionic-angular
my ionic project works fine with ionic serve --lab ,but while copied the.apk file in build folder to my phone and install the app but blank screen appears ,
Please can anyone suggest what might be my problem
my app is using google maps,key is provieded for both app and browser in index.html
Have you tried running it in the emulator ? Since its much easier to see the error logs . Try ionic emulate android -l or ios -l (whichever OS you are building for) and then once the execution starts run the command consolelogs it will log all the activity and you will have a better understanding about why its not working.
+1 for using Chrome Remote Debugging feature. It give you the same output as you would receive from running you app in the browser.
Additionally, I have found that sometimes if your app is already compiled, the ionic CLI doesnt always copy your current files into the APK, and uses the older cached files instead. If you are banging your head against the wall, run the following commands to make sure you have your latest code in your APK.
ionic platform remove android
ionic platform add android
ionic run android
I suggest you use the Chrome Remote Debugging feature. I encountered the same, and looked for answers to my symptom for hours. Once I connected to the chrome remote debugger, I got the console.log back, and noticed there was a problem in my routing setup.
It was a problem with ionic CLI. I've updated it to the latest and reinstalled all dependencies.