I've come across a specific issue that seems to have started happening in the very recent versions of Chrome, I can't specify the exact version when this started happening but I will try to fully explain the scenario.
I have a PWA application that is normally run in a chromeless window on an Android 7 tablet. When it is offline and all the applications files are cached (verified in devtools) it will not download cached PDFs. However, if I run the application in normal Chrome, still offline, the PDFs will download correctly.
The error (shown as a toast message) is simply "Cannot display PDF (xxx.pdf cannot be opened)" No errors show in the console. I added a console.log message to note when these PDF files are being served and it is only shown when not in chromeless mode.
if (requestUrl.pathname.startsWith('/Content/maps/') || requestUrl.pathname.startsWith('/Content/pictures/')) {
console.log("Serving pdf or image file");
event.respondWith(servePDF(event.request));
return;
}
To me, this indicates that something is different while running PWAs in chromeless mode and I cannot find a work around or fix for this issue.
Related
I've built an html5-video webpage that uses video-js and its chromecast-plugin. When I use the resulting cast button on video-js player's control-bar, when running on Chrome-browser on Android, it fails to completely transfer over to the TV's screen. The failing symptom is that only a large blue cast-icon is visible in the center of the TV screen. It fails on Android, each and every time I try it. (My Android is version 7.1.1, on a Google Nexus-9 tablet.)
And when it fails to completely cast over to the TV, the cast-icon-button on the video-js control-bar turns red, which I assume means that the chromecast-plugin 'knows' that it failed. (The videojs-chromecast-plugin is version 2.0.8)
My chromecast device is a 2nd-generation chromecast-dongle from Google.
[ From a PC-platform, the video-js chromecast-plugin's cast-button works perfectly every time. That PC-platform is Windows-10, using the newest version of Chrome browser (Version 63.0.3239.132 (Official Build) (64-bit)) ]
So, could someone with Android and a chromecast device please test my
webpage and report whether it works or whether they too fail with a large
blue cast-icon image in center of their TV-screen.
(Note: I've googled for symptom of the blue cast-icon in center of TV, and
find various reports of this exact symptom, on various platforms. But
none of those problem posts ever end with a solution, so I've concluded
that this is a known open issue.)
My webpage that is failing is located here:
https://weasel.firmfriends.us/HTMLVideoFromCloud/
[ You can see the page's html and javascript via "view page source"
in the browser (right-click anywhere on the page, outside of the
video-js viewer) ]
(EDIT#1) Ok, some extra clarification: The problem casting from Android happens ONLY when I use the cast-button at right-end of videojs-viewer's control bar.
But, I have found an alternative cast-button on Android, that CAN successfully cast my page to the TV. I don't recall exactly what I did to get this extra button to start appearing, but it will appear for a few seconds in the upper-left client-area of the video-js player window rendering my webpage. This 'workaround' doesn't completely solve my issue, because the goal is to get videojs-chromecast-plugin's cast-button to work. Also, other people viewing the page from Android may not know how to get that alternate cast-button.
(EDIT#2) I've tested now from two different tablets...both fail.
(1) Android version 7.1.1, on a Google Nexus-9 tablet
(2) Android version 5.1.1, on a Google Nexus-10 tablet
TIA...
I have deployed my app to play store. It is released on production. It works fine on google's pixel only. When I tap the link on Samsung devices I see instant app loading screen for few seconds (see the screenshot below) and the URL is handled by the browser (chrome in my case) instead of loading the instant app. However, buzz feed's instant app (https://www.buzzfeed.com/tasty) works absolutely fine.
Here (https://drive.google.com/file/d/1O1ZQkEcOUiTIkHZN3_QA94gTZCY-ppYo/view?usp=sharing) is the link to my log file when I tap the link. I don't see anything on Logcat.
I'm working with a special image format and was creating something to dynamically generate it. I went to try it in mobile Chrome (it isn't displayable in the browser but it could be downloaded) and suddenly it opened about fifty new tabs! I fought with my browser to close them all but it just kept creating more.
http://www.sudomemo.net/images/dynamic/profile/540417_0BC7C6632064B_047.ntft
There are no redirects, no scripts. It's an image.
Any clue as to why this is happening? Have I discovered a Chrome bug?
Google Chrome 39.0.2171.93 (Official Build)
Revision bec62c44cbc7da9f6a507873382ebc111d66e9d7-refs/branch-heads/2171#{#449}
OS Android 4.4.2; XT1031 Build/KXB20.9-1.10-2.27
Steps to reproduce: Tested on Android Kit Kat, with the only installed browser being Google Chrome.
Open Chrome and go to the above link.
I figured it out a while ago.
To make it short, mobile Chrome didn't know how to handle the file, as it had a text/HTML content type but wasn't parsable as text or HTML. It got passed to the Android Content Provider, (that bit which gives you options between which apps you can use to open something), which immediately returned it to Chrome, as it's the only browser on my phone, opening it in a new tab. This looped over and over, quickly causing my phone to slow down and crash.
I just want to ask if there is now a workaround to solve the file upload problem in Android when there's not enough RAM after file selection.
Look at these URLs:
Android browser refreshes page after selecting file via input element
http://code.google.com/p/android/issues/detail?id=53088
https://github.com/kostysh/File-uploading-component-for-Sencha-Touch/issues/5
My smart phone Samsung Galaxy xcover has 37,70 MB RAM.
When I click a standard HTML file upload control on a web page and select a file (from gallery, camera, camcorder etc.) Android kills the browser instance to get some free RAM, then Android starts the browser again and refreshes the web page.
I think there must be a technical solution some day ...
Has anybody new information about this problem?
Thomas
Major head scratcher happening today. I developed a Cake app, hosted on Pagoda Box, that runs fine on all browsers except Android native browser on the Galaxy S3. It displays a white screen:
http://broomage.pagodabox.com/sweepstakes/MetsMoments2013
However, I uploaded this app to a standard LAMP server so I could debug it more quickly, and it showed up just fine! See here:
http://epi.qa/broomage/sweepstakes/MetsMoments2013
I'm really mystified at this point, since it now seems specific to Pagoda Box. I've checked the apache/php/cake logs and nothing weird is showing up. I can also "view source" and see that everything seems to be loading properly--only the browser just shows a white screen. This problem also happens on certain sites that use the Bootstrap library, but will sometimes show up if you go to another URL then hit the back button. But this particular site just shows a white screen on the S3 no matter what I do. Any ideas???
Grrr, I think I narrowed it down to a gzip issue: If you are serving certain assets thru a php script, the size may be reported as a mismatch w/ the compressed size, which screws up rendering on lackluster browsers like that of android.