When I use chrome, google pay automatically suggests I pay using one of my saved cards.
This is working for my site on desktop but on mobile it is not.
It asks me to select my card
then to put in my CCV code
it then checks that it is correct
but it does not appear on the form when the google pay box disappears.
Is there a way to fix this or to disable google pay from suggesting using saved credit cards?
The site is live here: https://www.ticketglen.com/events/627169277aa4727312497eaf
I fixed this by upgrading to the latest version of react.
I was using version "^16.9.0" when there was a problem.
There is no problem with version "^18.1.0"
Related
I have the OpenCore Legacy Patcher on my 2010 MacBook Pro, and it's running great with all the patches applied. Google Docs and Sheets (maybe Slides too idk) are not working properly in chrome and microsoft edge. There are many issues, but sometimes I can't see what I typed for example. as such it has made using the google docs offline feature problematic. how do i resolve this?
i tried using user agent switcher in firefox but it didn't work. i am mainly interested in using google docs offline feature. i can use it online with firefox and safari but i do not always have access to internet and this has become a challenge.
this the google docs tab before i start typing.
this is the tab when i start typing.
sometimes everything this appears except what I'm typing
I decided to use the Housez theme as it advertises as super easy and flexible to use. I am not a web designer but have managed to get my site up and running. www.islandestates.net The problem I have is that there is no search option for the properties on a mobile device? The desktop version works well but how do I get a search box onto the mobile version?
The support from Housez is non existent, I have submitted a request to favetheme but they never reply.
Any help would be aprreciated.
Malcolm
My Google Chrome Extension (Annotate for Chrome) has successfully received payments.
I have updated the app recently but not the payment flow.
Now when a user initiates a payment the Google modal pops up (that displays the Google payment - from Buy.js) the spinner just runs endlessly and console shows a 401 error.
I double-checked manifest and in-app purchase SKU etc and don't see any differences from previous versions that worked. My check for current license is working fine - which tells me my app is being recognized by the Google Web Store and returning data on specific users license status...
Any thoughts on what could cause this? Many thanks.
(I submitted a ticket to CWS support - nothing yet). Probably something stupid but I don't know how to debug. Or epic fail on Google's part.
The root cause of this issue has been fixed and purchase flows should be working as expected now. Details over here: https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/bxoptYk8--Y/Mh_qJp4gDQAJ
This is a problem with the Chrome Web Store.
I tried to purchase another Extension (https://www.twinword.com/blog/how-to-quickly-monetize-your-chrome-browser/) that uses in-app purchases and saw the exact same problem.
So Google's Web Store purchasing process has been broken for a week+ and no one at Google cares. Maybe they should get out of the payments business and require developers use 3rd party solutions. Utterly disgusting on Google's part. I'd like my 6 hours of troubleshooting back...
My app is available on the firefox marketplace at https://marketplace.firefox.com/app/shopping-list/
However if I search for "shopping" or "shopping list" in the marketplace app or on https://marketplace.firefox.com it does not appear anywhere.
What is going on ?
Your app does not appear when searching the Firefox Marketplace from Desktop or Android because we filter search results to show only apps that will work on the device you are searching from, and you did not check the boxes to say that it is available on desktop or android. Like Jason, I easily found your app when searching from my Firefox OS phone.
Gi,
Marketplace reviewer here. Your app is public and has the following requirements:
IndexedDB, Smartphone-Sized Displays (qHD), Vibration.
You should be able to find it, no matter what version you are using.
My guess is that your are using any hyphen to look for it. If you try using "shopping", it will be in the third place:
I am looking for something that will help me learn how to set up my site so that when people go to it there is the regular version and the mobile version. Problem I am having is that most of the sites I see on google are pay sites that help you set that up. Can I just make two versions of my site and load them both on my hosting? Also how does it know when to load the mobile versus the regular? These are the types of things I am looking to learn, any suggestions of places to start?
Please please please make sure you do the following:
Only do a mobile version if it adds value.
If a user requests a deep link from a mobile device, don't redirect to the mobile home page
Allow the user to choose to view the full version
Make sure tablets such as the iPad uses the full version by default
Don't serve WML to the hi-res smartphones such as the iPhone
If your full sized website is unusable on a phone, consider tweaking it to be more suitable (don't print content text too wide).
Modern iPhones and iPads are perfectly capable of handling most full sized websites, there is little need for a mobile version unless it actually improves the user experience. I hate to get redirected to a baby interface that doesn't provide the information I need.
Good examples of mobile versions include:
Google website
Gmail website
Mediocre examples include:
Any blogpress site
Bad examples include
anything that uses WML
Here's Apple's advice on providing mobile versions to the iPad:
Note that the Safari on iPad user
agent string contains the word
"Mobile", but does not contain the
word "iPhone". If you are currently
serving mobile content to any browser
that self-identifies as "Mobile", you
should modify your user agent string
checks to look for iPad and avoid
sending it the wrong version of your
site. The version numbers in this
string are subject to change over time
as new versions of Safari on iPad
become available, so any code that
checks the user agent string should
not rely on version numbers.
Something to look into would be the #mobile css media type, which is used to load a different styles when loading in a mobile device. I am not sure which devices support it, but I imagine it would be most of the popular models. As far as your suggestion, you can certainly host two separate sites, but I would defiantly go through Alex's suggestions before you go through the trouble.
http://www.w3.org/TR/css-mobile/
Alex had some good suggestions, but if you really want to serve up a specific version based on mobile or non-mobile you can take a look at the http header. In some cases the User Agent will give it away, but not always. Check out this link for details: http://detectmobilebrowsers.mobi/