Ionic Capacitor page is flashing on some Android devices - android

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

Related

Android Studio SDK not showing support for Android 7.1.2?

I recently got notified from a user running the Xiaomi Remi 4x android 7.1.2 that my app is crashing. However on my Android 8.1.0 Samsung Galaxy Note 9 it is running just fine.
I tried to therefore download the 7.1.2 SDK however I can't even find it on the SDK Manager nor the AVD Manager. Has support for 7.1.2 been rejected or why can't I seem to find it?
I'm also currently running Android Studio 3.2.1
Android version 7.1.2 is not a separate platform/API level, it is just version 7.1 plus several functionality and security patches.
See the full list of Android API levels:
https://source.android.com/setup/start/build-numbers
If your app does not work on a Xiaomi device most likely the Android version is not the problem but the adaptions Xiaomi made to Android and/or an incompatibility regarding a certain driver (e.g. graphics).
Therefore most likely even if you could get an Android 7.1.2 platform you won't be able to reproduce the error. Therefore I see three options which may be possible:
Check if Xiaomi provides own emulator images for certain devices (not very likely but who knows)
Try to get a physical Xiaomi device of the same product branch
Use an online service that provides you remote access to a physical Xiaomi device for installing your app and debugging it. Such services are also known as "device farm"
Ask the affected user to provide StackTraces and then try to understand what is going wrong (and of course StackOverflow for the problem), provide test releases to the user. Redo this loop until the problem has been solved.

chrome inspector, remote debugging no longer works properly on my mobile app

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.

what is the available emulator to test android automotive app ( not android auto )

I am developing car launcher for infotainment system (not Android Auto) using AOSP (Android Open Source Project).
How can I test that application?
It is not possible to emulate Android Automotive at the moment. As you can see here, there's rumours of Google working on an emulator, but no news so far:
Two commits in the AOSP source code indicate the release of the emulator. One states the tag for Android Automotive image folders has been created, and the other mentions a test for “oc-car-m1″ emulator images. This likely stands for “Android Oreo Maintenance Release 1″, possibly being Android 8.1. If this is the case, then it’s likely we may see an emulator around the time Android 8.1 launches.

ionic 2 blank after splash page under android 4.3

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).

Having trouble running Chrome App in Genymotion Emulator with Google Play installed

I am trying to use Genymotion to run Android 5.0 (android version does not matter here as it fails for multiple). I installed Google Play (from here). All other apps work (and Chrome used to also) but I guess they made some update and now whenever I click on Chrome, the app crashes (screenshot below).
I am just looking for ANY solution that allows me to run Chrome app in Genymotion. Is there a way to get just the APK for Chrome to install in the Emulator? (Dont want to do native emulator as it is sooooooo slooowwwww)
This is caused by the newer versions of Chrome, so you can install an older version and it will work.
So first make sure that you uninstall the current Chrome version, and go to Google Play settings and TURN OFF the auto-update feature.
Then download this chrome version:
http://www.apkmirror.com/apk/google-inc/chrome/chrome-44-0-2403-133-240313311-x86-android-apk-download/
Drag it into the emulator and it will auto install it. That should work.
If you get an error like "INSTALL_FAILED_NO_MATCHING_ABIS", that means you need another version of Chrome, so go to www.apkmirror.com and look for your corresponding version of chrome. I've tried with the version from August 1 and it works.

Categories

Resources