My question is similar to ionic-mobile-app-gives-white-screen
I have created one ionic app that runs perfectly fine in a browser, but when I convert it into an app I am getting a white screen.
I have already installed the white list plugin and allowed all urls in the config. I also have kept the meta tag.
This is one ionic 2 application.
It runs perfectly in web and on all Android devices when I use ionic 1.
But, I can use Android 5.0 or higher version to run ionic2.
I have tried many methods such as how-to-debug-the-white-screen-of-death-in-your-ionic-app, but i can't inspect button for my debug
chrome inspect.
My android device: genymotion, htc one, running Android 4.3 (API 18).
Related
I made an application using ionic, first releases were using Cordova, but my last release uses Capacitor, now some customers are no longer able to use the last release on their Android phones(specially Tecno devices running on Android 8.1, Alcatel 1 devices,...), the application keeps blinking or flashing they can't click anywhere, for some it messes up the whole page like on the screen shots
The problem was du to Google Chrome latest version (92.0.4515.115), devices with PowerVR GPUs (GE8320 or GE8100) running on Android 8.1 were impacted. The bug has been fixed by Chrome Team.
You can follow the discussion on this link Issue 1222095: Icons not displaying after latest Chrome update on Android 8.1 devices
I'm trying to use readium 2 library for my android project. I cloned r2-workspace-kotlin repo. I launched the app on some of my test devices. I noticed that on one device the app is unable to render some pages. Instead of what should be a page of the book I get a page saying Webpage not available. The device is running android 7.1.2 but it's not related to android version as I tested the app on emulator running the same version and it worked. Anyone has any ideas how to fix it?
I have built a progressive web app using Cordova/Ionic. I have been using dev-tools to troubleshoot and analyze my apps inner workings for the better part of 3 years now. In the last few weeks however, i think since Chrome updated to v70+, dev-tools can no longer properly connect and/or manage the app running on my external device (several different test phones).
I have 4 Android test phones, and the same or almost the same issues are happening with dev-tools when connected to each device.
desktop keyboard and mouse do not work anymore - I can't use either to interact with the app on the phone anymore. As well, on some
phones I can't use the element inspector (while on others that does
work). But regardless of phone, I can't use the desktop mouse to
click on app buttons in the web-view. Keyboard does not work on any
of the devices either.
Often, even the native buttons in the app (directly on the phone) won't work if dev-tools has been opened to look at the app. If they
do work, you press the button and like 10-15 seconds later the app
finally responds.
When dev-tools is opened and connected to the device app, the response time of the apps is now extremely slow as well. Sometimes
the app just crashes or I get messages saying "app not responding,
wait or close?"
If I disconnect the phones from the desktop, and/or don't run dev-tools on the app, the app works and responds just fine. Something
specific to dev-tools is causing all these problems.
The different phones have versions 5.1, 6.1.1 and 7.1 running on them for testing purposes. Again, dev-tools worked just fine until a few weeks ago. I recall various small issues impacting performance and web-view rendering in dev-tools, and now all of the above is impacting my ability to troubleshoot and analyze my app (developing).
My environment:
Cordova CLI: 8.0.0
cordova-android: 7.1.1
Gulp version: CLI version 3.9.1
Gulp local:
Ionic Version: 1.3.4
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS: Windows 7 SP1
Node Version: v6.10.3
Chrome: Version 70.0.3538.102 (Official Build) (64-bit)
I can't be certain, but I think all these issues began with Chrome updated itself to v70.+ On a side note, my app uses the "webview-plus" plugin....its an older plugin that enables certain inspection features and UI rendering. I removed it to see if maybe it was conflicting with dev-tools, but all the same problems still persisted.
I have the same issue, it worked fine some months ago, but it is now broken.
As a workaround, I tried to disable screencast, restart the app and then restart devtools and it worked!
Hope this helps!
The real problem is the latest android webview. All the element selection and mouse click doesn't work in latest android webview.
So, uninstall the android webview from Google Play store.
Download the older android webview version around 60
install it via adb with -r flag
adb install -r "/path/to/apk/com.google.android.webview_60.0.3112.78.apk"
This is a workaround until it is fixed in the latest webview.
I have created a cross platform Xamarin Studio project for iOS and Android. Sources for shared code, Android and iOS all appear in the Solution browser. However only iOS simulators appear in the device selection popup for where to run the app. There is no Android options that appear.
I have tried creating and starting AVDs manually, but nothing shows up.
How do I run the app in an Android Virtual Device?
Change the Solution's Startup Project to the Android-based one and the Devices will change from iOS to Android devices:
I just installed Phonegap following all of the steps:
http://docs.phonegap.com/en/2.5.0/guide_getting-started_android_index.md.html
I installed the latest versions of:
Eclipse
Android SDK
ADT Plugin
PhoneGap
Cordova
I am using:
OSX 10.8.5
Everything runs smoothly but when I run cordova emulate android. THe emulator shows up and loads for a minute then says:
"Unfortunately, Workshop has stopped"
And the app never loads.
Also, when I run cordova serve android the browser shows an alert that says:
gap:["PluginManager","startup","PluginManager1650094558"]
Then the app loads and the browser will show the default cordova screen that says "Connecting to Device" but the app never reaches "Device is Ready". I have have tried tons of different approaches from downgrading versions to creating several AVDs to test. So far after a good 4 hours of testing I haven't found an answer.