Recently created a wordpress website, which works fine on the following:
Desktop.
iPhone on Wifi and 4G
Android on Wifi
On Android using 4G it simply does not want to load. I receive a
ERR_CONNECTION_CLOSED or HTTP ERROR 504.
I've tried optimization plugins and image resizing. Also removed a slider to see if that was the problem. I've tried Android browser, Chrome and Firefox all to no avail.
I'm quite a novice when it comes to code, so not sure where to start. Thought I'd try here to see if anyone can offer advice?
Related
I'm trying to turn my PWA (Progressive web Application) into an TWA (Trusted Web Acitivity) App for Android. In the beginning everything was working fine, until a user reported a problem to me.
He was unable to open the App at all, so we checked to see what could be the cause. Turns out he hasn't installed Google Chrome and is using Samsung Internet instead.
Now I did manage to get the App working with Samsung Internet so far, but with Samsung Internet the address-bar still appears.
There are a few tutorials to setup your TWA for Chrome OR Samsung Internet, but how can I combine these two? I guess we shouldn't force the user to download Chrome first. I haven't found any articles concerning this issue, so I'd be grateful if someone can link me some.
When using a Trusted Web Activity with the recommended android-browser-helper library, the application will check for an installed browser that supports Trusted Web Activity, giving preference to the user's preferred browser.
If there's no browser that supports the protocol available, it will fall back to using a Custom Tab and, if Custom Tabs is not available, open the browser.
The library also contains a WebView fallback for developers who prefer that to the Custom Tab / browser. A demo on how to use the WebView fallback is available here.
Regarding the Samsung Internet browsers, it added support for Trusted Web Activity in November 2020 (version 13.0.2.9). Currently, Chrome, Samsung Internet, Firefox, Edge and others support Trusted Web Activity, covering the vast majority of users. An updated list of browser support is maintained here.
After tons of wasted time trying to figure this out myself and lots of research I found this article:
https://medium.com/#firt/google-play-store-now-open-for-progressive-web-apps-ec6f3c6ff3cc
Where you can find this info:
TWAs work only with Chrome today, but the API might be also cloned by other browsers, such as Samsung Internet, Edge or Firefox in the future.
*UPDATE 2/4: The TWA works over the Android Custom Tab protocol that other browsers are currently implementing, so if the user doesn’t have Chrome or has changed the default browser, another browser might take precedence and open the TWA with the PWA content. More testing is needed to understand how it works.
What happens if the user has an older version of Chrome and installs the app from the Play Store? In this case, your PWA will appear as a Chrome Custom Tab, not in a completely standalone mode.
What that means in a nutshell: TWA's are actually useless, as long as you need your App to be compatible with a lot of different devices (like most do). I also noticed many Apps don't work if you disable Chrome on your Device, why I guess these are using TWA's too (and getting bad reviews on PlayStore instead).
So what I did was to dump away everything I did with TWA, and simply started using Cordova instead. It would have been great to have something like TWA's working just that simple, but as long as it's not working without having Chrome installed, there's no point in using it at all.
And not having this stated on https://developers.google.com directly, but fuzzy and unclear, has probably ended in the waste of time of many dev's and/or tons of Users being unable to use some Apps.
I just checked my TWA and it is working for particular browsers as follows:
Chrome without any problem
Edge on first launch shows message running in edge, later works as expected
Opera working as expected
Samsung browser - asks to open in browser, but works fine in browser. hides address bar if opened in browser
Firefox(once a best browser around ...) asks to open in browser, if opened it still shows address bar
I built a website in Rails and it is rendered properly on most major browsers, on computer and phone. However, on my phone (an LG G3) which has a browser called Internet (version 5.2.34b13) I can't open navbar, I can't sign up and some other small features are not there. On the same phone it works fine with Chrome.
Has anybody had any similar problems? How can I fix this?
Jello Al-Josh!
It sounds to me like it is a cross-browser issue and has nothing to do with Rails. I'd recommend you to use the Autoprefixer gem ( https://github.com/ai/autoprefixer-rails ) to sort out CSS vendor prefixes issues.
I been putting together some of the CFWEBSOCKET demos I found on the web. I can get them working on iOS and with different browsers fine. Yet when I try my Android phones S3 and Xoom they don't connect correctly with any of the Demos I found online.
I been searching but don't see any comments on using CFWEBSOCKETS for a Android Phone Web Application. Has anyone ran into this issue? I see Websockets work using the Echo Test from Google so it has to be something with CFWEBSOCKET coldfusion tag.
I don't have an Android phone or tablet, and it seems that on some Android devices using stock browser my website is stuck for half a minute until it loads.
I've been testing with various emulators found online like BrowserStack, etc. The browser is just stuck for a while. That's not the case for iPhone or desktop.
How can I debug this issue? How can I see a developer console or errors or figure out what's causing the slowness?
You can use Remote Debugging with Chrome for Android if the problem happens on this browser (which is the default browser on recent Android versions)
How to use Remote Debugging with the emulator
If the issue only occurs with the legacy Android browser, you might be able to get some information by monitoring the http requests with Fiddler
How to use Fiddler with Android
These links will help you debug code in general without having a physical android.
Android studio user guide on debugging: Start, Projects and Tools.
Google developers page.
So I am currently having this problem of trying to open up our web app on the official stock Android browser for Jelly Bean. I don't know how well I can elaborate this problem, but I will try my best.
For devices that run ICS or older, on any browser (stock, firefox, chrome) we can type in the URL for our web app, get taken to the login page, login, and view everything fine.
For devices that run Jelly Bean (4.1 and 4.2), if we type in the url into the stock browser, we get the following:
However, if we use Chrome or Firefox, its fine.
It's odd that we get this error because I am already authenticated on our network, and I only try to access the login screen so no other authentication would be required.
Our web app grabs information from a server, and it doesn't seem to be a problem on the server side.
So it seems like the culprit is the stock browser in Jelly Bean, and I tried looking up if there were any changes to the stock web browser from ICS to Jelly Bean, but I couldn't find anything yet.
Has anybody come up with an issue like this, or is aware of any big changes (maybe related to security?) that were made to the stock android browser on Jelly Bean?
EDIT: This web app is not available externally. Currently we have only tested internally where you would have to be connected to our internal network.
EDIT2: Just checked with Dolphin Browser and the same thing happened... so I'm really lost now as I am even less sure that it has something to do with the 4.1+ stock browsers. Also, something else that makes me feel even more lost is that, I just checked on the galaxy SIII's stock browser on 4.1.2 and the page loads fine...
EDIT3: Good news, further investigation has been done by our devs and apparently this is the problem:
the default browser adds an extra header to the request that makes our server think it is an ajax request and rejects it because the rest of the request is not actually an ajax request... This bug is caused because the default browser in Android 4.1+ has added a new header to all requests "X-Requested-With: com.android.browser".
So I'm guessing the Dolphin HD browser does this as well... further investigation is being done so will get back to this and put up an answer
According to our devs who did some research:
the default browser adds an extra header to the request that makes our
server think it is an ajax request and rejects it because the rest of
the request is not actually an ajax request...
This bug is caused
because the default browser in Android 4.1+ has added a new header to
all requests "X-Requested-With: com.android.browser".
At the moment we can't afford to spend more time trying to find good work around through code for this problem... so we decided to document this as a known issue and suggest people to use Chrome if they have a 4.1+ device