I'm experiencing a bug in GoogleChrome's Trusted Web Activity feature. We've launched a Progressive Web App in the app store using TWA and it runs fine on Android Version 10 (API 29). On other versions of Android it shows a toast message reading "Please install Chrome Stable 72 or later". This occurs on older and new versions of GoogleChrome.
Has anyone experienced this bug before?
When i tried to log a bug report on the Google Chrome's Github they say the best place to ask questions about TWA's is on StackOverflow.
I currently have a java project which instantiates various browsers via selenium hub/node on various windows operating systems. Is there much involved to expand this to cater for running up a browser on a stock chromebook chromeOS?
The following are steps I tried back in November 2014. The result was unsuccessful and I opened a question on the Google forum with no response.
followed manufacturer's instructions to put the Chromebook in Developer Mode
set chromeos-firrmwareupdate to dev mode and removed rootfs verification from partitions 2 and 4
downloaded and installed Java (latest jre), required for Jenkins slave and Selenium
downloaded Jenkins slave.jar and selenium-server-standalone.jar (2.41.0)
put Jenkins and Selenium in /home and remounted to remove noexec
remounted tmp to resize to 2G (req for Jenkins)
added DISPLAY=:0.0 to ui.conf to set display
added chain rule to allow tcp input
added 'no-sandbox' and 'disable-setuid-sandbox' switches and excluded 'test-type' switch
Result: ChromeDriver started up, opened up a gray screen (a broken instance of Chrome), and closed with an "unable to open pages" error. Weird thing, though, was that the same command used to launch Chrome worked when run from the terminal.
Ever since I upgraded my Samsung Galaxy S3 to android 4.3 (from 4.1.2) I am unable to use Chrome's remote debugging for android (more details here).
I have the developer options and USB debugging enabled on my phone, and this worked perfectly fine on android 4.1.2.
Now, when I connect my phone to my PC, it simply connects as a media storage device and is not discovered as a USB device by chrome.
I am ruling out any problems with chrome as I could USB debug with a Google Nexus4, also, looking at some other thread (here and elsewhere) it seems to be a problem with Samsung's 4.3 upgrade.
Any pointers to get this working?
My devices stopped working as Chrome de-activated the now depracated ADB plugin as it's built in dev-tools now.
I downloaded the SDK and followed the instructions at Chrome Developers. How ever I found the instructions served by Alphonso out not to be sufficient and I did it this way on Windows 8:
Download Android SDK here ("SDK Tools Only" section) and unzip the content.
Run SDK Manager.exe and install Android SDK platform tools
Open up the Command prompt (simply by pressing the windows button and type in cmd.exe)
Enter the path with ex:
cd c:/downloads/sdk/platform-tools
Open ADB by typing in adb.exe
Run the following command by typing it and pressing enter:
adb devices
Check if you get the prompt on your device, if you still can't see your phone in Inspect Devices run the following commands one by one (excluding the ")
"adb kill-server"
"adb start-server"
"adb devices"
I had major problems and managed to get it working with these steps. If you still have problems, google the guide Remote Debugging on Android with Chrome and check for the part about drivers. I had problems with my Samsung Galaxy Nexus that needed special drivers to be compatiable with ADB.
Update
If you are using Windows 10 and couldn't find the link to download Android SDK; you may skip #1 and #2. All you need is activate "Android Debug Bridge". Go straight to #3 - #7 after download and execute "platform-tools"(https://developer.android.com/studio/releases/platform-tools.html)
Having attempted to follow Valros.nu's answer, i discovered that the sdk download is now bundeled with androind studio, in an 840MB exe installer.
As all you need for this particular program is the adb program, you can get this in a standalone installer from the xda guys:
http://forum.xda-developers.com/showthread.php?t=2317790
Note that you do not need to type adb.exe, simply type adb devices into the command prompt that is launched after install.
Also, i had to unplug and replug in my samsung s4 to get the remote debugging prompt to appear on the phone
After looking around a little longer I came across this. Apparently, there isn't a solution to this issue yet, but there is a workaround - going back to the legacy workflow.
The legacy workflow did work for me, and the only additional thing I had to do was to go to the platform-tools folder from android SDK download, open a command window here and run command "adb devices".
This caused the computer RSA key fingerprint panel to pop on my mobile screen, and after granting permission, the device showed up under Chrome's Inspect page.
Turns out that it was not an issue caused by mobile OS upgrade but by Chrome (I was thrown off by the fact that it worked on my Nexus4 somehow).
In the older versions of Chrome there was't a need to download the 500 odd mb Android SDK, as it supported an ADB plugin. But with latest version of Chrome, I guess, going legacy is the only way to go.
I have Samsung Galaxy S3 and it was not showing in the "Remote devices" tab nor in chrome://inspect.
The device did show in Windows's Device Manager as GT-I9300, though.
What worked for me was:
Plug the mobile phone to the front USB port
On my phone, click the notification about successful connection
Make sure the connection type is Camera (PTP)
On my Windows machine, download installer from https://github.com/koush/UniversalAdbDriver
Run it :)
Open cmd.exe
cd "C:\Program Files (x86)\ClockworkMod\Universal Adb Driver"
adb devices
Open Chrome in both mobile phone and Windows machine
On Windows's machine navigate to chrome://inspect - there, after a while you should see the target phone :)
I'm not sure if it affected the whole flow somehow, but at some point I've installed, and later uninstalled the drivers from Samsung: http://www.samsung.com/us/support/downloads/ > Mobile > Phones > Galaxy S > S III > Unlocked > http://www.samsung.com/us/support/owners/product/galaxy-s-iii-unlocked#downloads
For me the solution was to download the Android SDK and launch adb devices which started the adb daemon.
I know this is an older question, but I thought I would also post my solution:
Update your Chrome on your phone and on your PC.
Even if it says you have the latest driver for your device inside
Device Manager, you may need an alternative. Google latest Samsung drivers and try updating your drivers.
I had success after using ade.exe as explained above, plus using the latest version of Chrome Canary. Apparently your desktop version of Chrome has to be higher than the version running on your Android device.
For me, the menu item Inspect Devices wasn't available (not shown at all). But, simply browsing to chrome://inspect/#devices showed me my device and I was able to use the port forward etc. I have no idea why the menu item is not displayed.
Phone: Android Galaxy S4
OS: Mac OS X
In case it helps anyone I will post what worked for me.
I had to plug my S3 into a direct USB port of my PC for it to prompt me to accept the RSA signature. I had my S3 plugged into a hub before then.
Now the S3 is detected when using both the direct USB port of the PC and via the hub.
NOTE - You may need to also run adb devices from the command line to get your S3 to re-request permission.
D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
9283759342847566 unauthorized
...accept signature on phone...
D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
9283759342847566 device
Those who updated their device to Android 4.2 Jelly Bean or higher or
having a 4.2 JB or higher android powered device, will not found the
Developers Options in Settings menu. The Developers Options hide by
default on 4.2 jelly bean and later android versions. Follow the below
steps to Unhide Developers Options.
Go to Settings>>About (On most Android Smartphone and tablet)
OR
Go to Settings>> More/General tab>> About (On Samsung Galaxy S3,
Galaxy S4, Galaxy Note 8.0, Galaxy Tab 3 and other galaxy
Smartphone and tablet having Android 4.2/4.3 Jelly Bean)
OR
Go to Settings>> General>> About (On Samsung Galaxy Note 2,
Galaxy Note 3 and some other Galaxy devices having Android 4.3 Jelly
Bean or 4.4 KitKat)
OR
Go to Settings> About> Software Information> More (On HTC One or
other HTC devices having Android 4.2 Jelly Bean or higher)
2. Now Scroll onto Build Number and tap it 7 times repeatedly. A message will appear saying that u are now a developer.
Just return to the previous menu to see developer option.
Credit to www.androidofficer.com
I'm interested in using Chrome (Packaged) Apps for ICT4D applications.
Is it possible to distribute Chrome Apps without being online / using the Chrome Web Store at all?
The big goal would be to distribute packaged apps using only USB flash drives / pendrives.
I would like to use Chrome Apps for their ability to target all desktop (& laptop) OSs. (Even fairly old ones. I might have to also distribute Chrome with the app.) Using web technologies (and laptops / computers) makes sense for the content-creation part of the app (and to reuse code), I think. The data could be distributed with the app in one neat offline bundle.
I will target mobile OSs with a simpler content-consumption app, but will probably try to reuse a lot of the code. In Android at least the app might be able to simply keep an .apk copy of itself to distribute to others offline.
You could put an platform specific Autoruns on the USB stick that run chrome with the --load-and-launch-app
Windows
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --load-and-launch-app=.
C:\Program Files\Google\Chrome\Application\chrome.exe --load-and-launch-app=.
Mac
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --load-and-launch-app=.
Linux
/opt/google/chrome/chrome --load-and-launch-app=.
I am using the latest subscription version of FDT 64 bit (with a subscription, not the free version). I have my FDT workspace and project files saved in my Google Drive. I am trying to work on the same FDT project from two computers: A Windows 7 desktop, and a new MacBook Pro.
Disclaimer: I am new to FDT, since just getting the MacBook I am trying out moving from FlashDevelop to FDT so that I can have a native IDE on both my desktop and laptop.
I created the project and started working on it while going through FDT tutorials on the Windows 7 desktop. Compiling, debugging, everything was working great. I am now trying to open the project and work on it from the MacBook. Upon launching FDT and choosing the workspace in Google Drive (which has finished syncing) I can see the project in the FDT Explorer, but if I try to open it by double-clicking on it I am presented with the error:
"'Open Project' has encountered a problem. The project description file (.project) for 'My Project' is missing. This file contains important information about the project. The project will not function properly until this file is restored."
However, showing hidden files and browsing with Finder shows that the .project file is indeed there, as well as every other file in the project's folder. I compared the contents of the files on the PC and Mac, and they appear to be the same.
Other notes: Both the desktop and MacBook have the 64-bit version of FDT installed.
My desired outcome is to easily move from my Windows desktop to my MacBook and continue working on the same project. Perhaps I'm doing it all wrong with trying to use Google Drive and setting the workspaces to be the same. Please critique and tell me how I should be doing it :)
After doing more research based off of the comments on my question, I decided to use a version control system instead of a network drive. A shared network drive is just not the right workflow for something like this, and corrupted files will always be an issue. I am now using BitBucket: https://bitbucket.org/
See here for more related information:
DropBox as Version Control and Offsite Backup
Update: For anyone getting started with Bit Bucket, this is what I used to get started:
This tutorial: http://www.youtube.com/watch?v=pp2S2lHjzZI (it's for Git Hub but works fine with Bit Bucket)
I am using TortoiseGit on windows, and Tower for Mac.
Few things you should confirm on your Mac to resolve the problem (in Terminal):
Check if the file is there ls ~/Google\ Drive/[your_project]/.project
Change file rights for the file sudo chmod 0777 ~/Google\ Drive/[your_project]/.project