Webview avoid security alert from google play upon implementation of onReceivedSslError
We have done the steps written in the above link.
And we have confirmed that the alert was removed on March.
But on April 22nd, we got the same alert from Google Play.
We have confirmed that our APK is still showing the SSL alert correctly on the device.
Has Google changed their policy?
Sorry we've found out that our APK had another webview, which we are not currently using.
And that did not have the SSL alert, so that was the problem.
Related
Is there a way to enable Google/Apple Pay to be invoked from a WebView? I'm using a payment service (similar to Stripe) that will gives me a payment URL. To finish a payment, I have to open a browser, navigate to that URL and let the user pay.
I'm using a WebView because I need to be able to intercept the browser navigation and close it when it's navigating to the return URL I've provided to the payment service. That's why I'm not opening the URL in a browser intent.
The problem is that when opened in a WebView, clicking on the Google Pay button fails to open the Google Pay overlay (where you can pick a card and pay) and the payment cannot be finished. I suspect that the WebView isn't able to invoke the Google Pay API, is there a way to enable that? If not, I'd have to switch to opening the payment URL in a browser intent (using the Xamarin.Essentials's Browser API) and I'd lose the option to intercept the browser navigation.
Thanks for any advice!
EDIT:
I've received advice from the my payment processor in the meantime. They said:
Use the Chrome Custom Tabs for Android instead of the WebView. It works similarly but also supports standard functionality (such as Google Pay). To use Apple Pay on iOS, use the SFSafariController.
I'll try that and report back here.
I have a React web app. I set up analytics as described in the documentation here : https://firebase.google.com/docs/analytics/get-started
With the help of the Analytics extension in Chrome, and in my dev environment, I can see the logs in the Debug view section. That means I setup analytics correctly in the app (I believe).
However, if I deploy my app to my https://myapp.web.app domain, nothing logs. I checked the Hosting section, and my app is correctly deployed and it is selected.
I updated my firebase sdk recently (8.7.0), and I added measurementId in the settings, although the doc says it's optional to use measurementId.
Am I missing something ? Is there any way to see if I'm missing something ?
Enabling Google Analytics involves API requests to Firebase Installations Service, to google-analytics.com and to googletagmanager.com`.
I use Firefox, because Chromium sends my computer CPU and RAM consumption to the moon, even with a single tab open. And in Firefox, unlike Chromium and Brave, among other browsers, I had nothing logged in the console.
Chromium and Brave logged API requests errors.
So, you need to add the Firebase Installations Service API key in the cloud console.
I feel this could be mentioned in the documentation, because it's not very obvious.
Anyway, someone explained it very clearly here : Firebase: 403 PERMISSION_DENIED (FirebaseError: Installations): Requests are blocked, after updating SDKs (FirebaseInstallationsService)
Now Firebase Analytics show logs when using Chromium.
However, these requests are blocked using Firefox and Brave (and therefore no logs are shown in Firebase Analytics). My understanding is it has to do with default settings in the browser.
With Brave, it's GET requests to googletagmanager.com/ that are blocked.
With Firefox, it's POST requests to google-analytics.com/ that are blocked. The above mentioned GET request is NOT blocked by Firefox.
https://rankfuse.com/blog/firefox-browser-blocking-google-analytics/
Does anyone know of a workaround ? I understand some Internet users can be annoyed by tracking systems such as GA, but Internet services need such tracking systems to improve their overall user experience, and if Internet browsers block analytics services, we are kind of stuck there.
EDIT: ok, so a bit of research about the above issue of browsers blocking analytics requests I came across various paid services purposely defined as workarounds and various tricks to bypass analytics blocking.
One straightforward way is to obviously proxy requests from your user's browser to google-analytics.com. There is a good article here that explains how to proceed can be found here: https://iainbean.com/posts/2020/the-shady-world-of-google-analytics-proxying/
Good afternoon! I want to confirm the integromat app in the Google app to upload my own files to Google Drive. Moved to the moderation stage, but the message "Comply with domain verification requirements"appears. Tell me, how did you solve the problem of checking the application in the google cloud app and the integrator service in order not to reauthorize the application every 7 days?
Assume that you already verified your domain and still getting this error, try to do this:
Go to your "Google Console" > "OAuth Consent Screen" and under "Publishing status" click "Back to testing"
Now you are back in the test mode, click "publish" again
You may see some new demands to publish it, which were unknown before. You could follow these demands now.
After that, you will see "The Trust and Safety team has received your form." message.
5I'm creating a google actions for Google Home, i'm using dialogflow and firebase functions and database to create the all thing.
So far everything was working good together but yesterday an error occured that i dont understand.
When i want to test my agent on the Simulator section of Google Actions, the agent is not responding even if in the logs i can see that the response is actually received by the simulator as shown here
And it answer this in the simulator
The response is empty and i have this simple error in the Debug section
It worked perfectly before but i may have change one thing that crashed everything and i can't find it.
EDIT
As recommended by #Prisoner, i've checked the History to find this
So i checked the logs and i got this (after Dialogflow Request and Dialogflow fulfillment request who were looking good)
It seems that the Dialogflow fulfillement response is having problem with URL ???
EDIT2
My URL fulfillment (firebase functions) was wrong, now that i have changed it, the log in my History seems ok :
But i'm always getting the same error on the Simulator.
Your logs show that your fulfillment is not deployed correctly and the URL is pointing to a HTML 404 page. This will cause your app to stop responding.
You may be running into the recent "first TTS is not spoken" bug in the simulator. I suggest changing your surface to speaker instead of phone. You can read more about this here.
When I go to my site on mobile it almost instantly shows up as an active user on google analytics. But when I do so on PC it never shows up as an active user. Even tried going to the site through Rabb.it
Also it shows active users 1 but "no data has been received the last 48 hours", does it just take time to update?
Have you looked at the JS debugger on your PC browser? Maybe there is an error that is causing the script to load incorrectly?
I've seen Firefox block the actual HTTP request to the analytics tracker, for example if you have private browsing turned on. I would start with using either Chrome's Developer tools or Firefox in conjunction with Firebug to try to take a peek under the covers as to what is occurring, i.e.
Verify that the JS actually loads correctly
Check for debug errors on the JS console
Check to see if the HTTP request is actually going through.
If your browser is blocking it you will see something like the image below.