I am using Chrome Version 110.0.5481.77 (Official Build) (x86_64) on macOS 13.1
I found some network resources have gear-icons before them:
I try to zoom in and notice the icon is a gear-icon.
What does this mean?
⚙ symbol means this request is made by a worker or a service worker (source code).
Related
I run "ionic cordova run android" using visual studio code.. but the apps shows white screen in the emulator.. it display properly if using USB debugging.. the device also display properly if install using the apk.. the reason why I want to use emulator because I want to debug "http://10.0.2.2".. this is my emulator setting..
Emulator setting
Things that I have done is as per below
Choose ANGLE (D3D11) for OpenGL ES Renderer at the emulator advance setting
Choose Software - GLES 2.0 graphic for the Emulated Performance during create emulator
Try both R and Q for the system image during create the virtual device
Update the SDK based on the system image set at the emulator
System image selection
Issue
I compile the source code at different laptop (Laptop A) and it manage to display error at the web console using google inspect
it display "newtrustedfunctionforjit fn.bind is not a function"..
Founding
the issue is related to the chrome version 83 and the browser need an upgrade to solve the issue
The emulator is not using a browser (it using web view) hence I cannot update the google version
Solution
download new skin for newer android model into laptop A
download same skin on the laptop B (the laptop that I initially come with this post)
Below is the explanation from GitHub for angular
Explanation about the chrome issue
Below is my new System Image
Release Name S
API Level 31
ABI x86_64
Target Android 12 (Google APIs)
New System Image
If I'm on a plane or do not have connectivity, remote debugging Chrome on Android fails with a blank window. What can I do?
When you remote debug, Chrome need a version of devtools that matches your mobile browser version. So it loads that specific version off the network. Once they are downloaded, they are kept in AppCache, so you only need to have network available once.
So as long as you start debugging a device (that particular Chrome version) once while you're online, you should then have all those files available later when you're offline.
But there's another workaround to avoid downloading the devtools version:
follow the instructions of https://developer.chrome.com/devtools/docs/remote-debugging-legacy down to (and including) the adb forward tcp:9222 ... section.
open http://localhost:9222/json/list (on your desktop)
find the tab you care about and copy the webSocketDebuggerUrl of it
wsurl = webSocketDebuggerUrl.replace('ws://','')
open this URL (on your desktop):
chrome-devtools://devtools/bundled/inspector.html?ws=${wsurl}
This will use your desktop's locally installed version of DevTools to inspect the phone. There is a possibility of a compatibility problem, but hopefully it should be small.
I faced some situation where the web app I developed worked differently (with errors) in a portable device than in computer. Then some googling took me to Inspect device feature of Google Chrome. After successfully connecting the phone to PC, I just clicked the inspect link for the corresponding tab.
Some internet resources said that some appspot link must be accessible. And, I verified it too. It is accessible from PC.
One mentioned try to open another inspect element window from the momentary devtool window by hitting Ctrl + Shift + I. It worked once out of many times and closed after a few seconds.
Configuration
Development system: Chrome 51.0.2704.19 dev-m (64-bit) running on Windows 10
On Device: Chrome 49.0.2623.105 running on Android 4.4.2
PS: Please, comment if any additional resources required to solve this issue
I am new to both the android and android development so I'm not on familiar ground here.
When I start the emulator I have no service. Therefore I have no internet connection on the emulator.
I am running Windows 7 and I generally run the emulator via eclipse.
My host machine is connected to the internet via the Local Area Network. There is no proxy.
I have tried:
Disabling all network adapters except for the Local Area Network [link]
Running the emulator from cmd line with: emulator -avd -dns-server 8.8.8.8
Reinstalling the SDK Tools 9 and Platform Tools (rev 2).
Restarting the machine! :P
Is there a setup needed to specify to simulate a 3G connection? Or could this be a Windows 7 permissions issue? Or am I doomed like these folks: link link
Ah! found the solution.. I uninstalled the entire SDK and reinstalled it to C:/Android. I deleted the C:/Users/[your-name]/.android folder and recreated an avd. Voila.. Something in there worked!
[edit]
Actually it looks like you have to keep restarting the emulator until it connects. I will often get no service so I restart a bunch of times till it works.
I found that 'Airplane Mode' was enabled by default in the standalone android emulator - this may also be the cause in the sdk version. Turning this off (by holding down the red power button until the menu came up, and then toggling the airplane mode button/section) allowed the emulator to 'find service' and connect properly through the LAN.
I have been trying to run the Emulator (Android 2.2 - Level 8) with Google APIs level 9 to test my License Checker implementation to no avail. This is as recommended at: http://developer.android.com/guide/publishing/licensing.html#test-env
It runs fine on the device, but not on the emulator.
On my AVD emulator, I don't have the Market installed. So I am not sure if the documentation is wrong because the architecture does show the dependency on the Market.
Has anyone had any luck running the LVL code on the emulator?
Thanks.
Sounds like you are trying to run Emulator with a target of "Android 2.2 - API Level 8". In order to get the LicenseChecker to run, the target for your Virtual Device needs to actually be "Google APIs (Google Inc.) - API Level 8". This will still open up the emulator for 2.2, but will have the Google APIs ready to use.
From the Licensing page:
To set up an emulator for adding licensing to an application, follow these steps:
Launch the Android SDK and AVD Manager.
In the Available Packages panel, select and download the SDK component "Google APIs (Google Inc.) - API Level 8" (or higher) from the SDK repository, as shown in the figure above.
When the download is complete, use the Android SDK and AVD Manager to create a new AVD based on that component, described next.
In the Virtual Devices panel of the Android SDK and AVD Manager, click New and set the configuration details for the new AVD.
In the dialog that appears, assign a descriptive name to the AVD and then use the "Target" menu to choose the "Google APIs (Google Inc.) - API Level 8" as the system image to run on the new AVD. Set the other configuration details as needed and then click Create AVD to finish. The SDK tools create the new AVD configuration, which then appears in the list of available Android Virtual Devices.