I have implemented plugin for google checout payments but now i see the notice on google developer documentation that google checout is no longer available from november instead they released Google Wallet.
My question is :
Is Google checkout and Google Wallet API same or i will have to change the API for google wallet ?
Google Checkout has been retired and will be shut down on November 20, 2013. You will have to change your integration. The announcement below has more details and options for migrating your payment processing:
http://googlecommerce.blogspot.com/2013/05/an-update-to-google-checkout-for.html
Different new Google Wallet APIs (such as Wallet Instant Buy or Wallet for digital goods) are available that allow you to accept online payments for physical goods, digital goods or services. A list of the available APIs and documentation is at:
https://developers.google.com/commerce/wallet/
Also see this answer for a good explanation of the differences between the Instant Buy and digital goods APIs.
I got answer from Google Developer.
I have contacted them and they told this are totally different from each other and they will released new API for wallet as soon as possible. :)
They are obviously different - otherwise there would be no point in the transition but there may/should be a fair amount of overlap between the two APIs. Some good places to start looking at the differences is here and via the Android Studio.
Related
What is Oracle Cloud Marketplace? Is it something like Google Play
Store where many apps are available to download?
When everything else fails, read the documentation.
Oracle Cloud Marketplace is an online store—a one-stop shop—selling hundreds of business apps and professional services that complement your existing Oracle Cloud implementation.
All apps and services on the marketplace are offered by approved, registered, and expert partners and developers. Plus, Oracle has vetted, reviewed, and approved each product.
I have published my app ("Match4app") recently with multiplayer feature, after months of hard working, using the Multiplayer APIs in Google Play Games Services.
Now, I received an email from Google:
Real-time multiplayer in Play Game Services is going away on March 31, 2020.
We’d like to inform you that on March 31, 2020, the real-time and turn-based multiplayer APIs in Google Play Games Services will no longer be available.
Action required
Because some of your games use one or both of these APIs (listed below), you’ll need to find replacements in order to continue offering multiplayer experiences. Migration options include using Firebase Realtime Database for multiplayer hosting and Google Cloud OpenMatch for matchmaking. You can log into your Cloud account to use Firebase Realtime Database for free with the Spark Plan.
We know this change requires extra work on your part, and we thank you for your understanding. If you have any questions or concerns, please let us know by filling out.
Questions:
How difficult is this "extra work" to migrate my game to "Firebase Realtime Database" and "Google Cloud OpenMatch" ?
Is there any tutorial with simple step-by-step instructions such as "1. replace mGoogleSignInClient.silentSignIn() with "FirebaseSignInBlaBlaBla... 2.replace this by this, etc." ?
If there is no simple migration and this requires an implementation from the scratch, is there any tutorial to make a multiplayer game with "Firebase Realtime Database" and "Google Cloud OpenMatch" ?
This "Spark Plan" seems to be free. However, this comes with limitations according to this link:
https://firebase.google.com/pricing/?hl=vi
Simultaneous connections: 100.
Is there any other "free" alternative, similar to the deprecated Google APIs ?
Answers:
There's lots of work to do. It's a re-write from scratch.
No. You still need to sign in, but you need to do a whole lot of OAuth stuff in order
to authorise your client via Google Play Services and your Firebase database.
There's a few youtube videos on it, but they always go the easy route of providing random opponents. None of them provide a player search if you want to play against a certain opponent (like GPG used to do).
Not that I could see. I'm moving our game to random players as there seems to be no real solution. Google Cloud OpenMatch seems very nebulous. I can't work out if it's a backend only, or whether I have to install it on my own server.
recently my company started using Bitrix24 as an intranet portal. Our employees use google drive and calendar synchronization between their google accounts (private ones, not gsuite). Few days ago I received an email from google:
We have contacted Bitrix24 support, but they could not give us any specifics with regards to this email and pointed out to contact google. Free google plans do not really have helpdesk support and point to sites like stackoverflow for help.
We do not really know what to do in this situation, as we have very little knowledge about google developer console. One of us just used his account to set up a project and provide OAuth to sync google accounts with bitrix24.
Several months ago google started releasing security changes enacted to help ensure that users data is secure. Due to this all developers with applications running risky scopes must apply for application verification
The developer who has created this application, probably the same person who received that email must click the link and submit the application. Once your project is approved you will not have any more issues. I suggest you begin the process now as it may take sometime for you to compete the process.
Even after enabling credit card information, Google Places API Quota is not increased. I am getting an error status of "over_query_limit". Can someone please help me fix this.
Google Cloud platform has a Billing support channel. This service is free of charge and you can file a support case related to issues with Billing accounts using the following web form:
https://support.google.com/cloud/contact/cloud_platform_billing
Feel free to reach out to Google support agents to solve your issue.
I have read about new Google Apps Marketplace and have seen the overview video here.
I'm worried about migration from OAuth1 to OAuth2 and having impact to some developed applications with APIs in my domaine
in the video exactely in 24', comparaison of what libraries/APIs are used in the OAuth1 vs OAuth2, and in 27' talking about turning off the OAuth1.
these Libraries/API will be deprecated ?
Any idea about turning off the OAuth1 and when ?
You need not worry about the impact of OAuth1 to OAuth2. This transition can be completed in a max of 15 days if you have done many integrations with Google. If you are worried just about the SSO with OAuth2 this can be completed in a day as Google has already provided proper documentation regarding the work flow.
Google has even provided migration APIs to upgrade your customers domains from v1 to v2 of Google Apps Marketplace(GAM). If you have a huge user base to be migrated then you need to plan accordingly such that migrated and non-migrated users would be able to use your app for some days till the migration is completed successfully.
Google will announce if it intends to discontinue or make backwards incompatible changes to this API or Service. Google will use commercially reasonable efforts to continue to operate those Google Documents List API versions and features identified at http://developers.google.com/google-apps/documents-list/documents-list-api-list without these changes until April 20, 2015, unless (as Google determines in its reasonable good faith judgment):
So on a safe side it is better to migrate all of your APIs to the latest libraries to avoid any failures at a later point of time. Anyway the older versions are not supported for any issue fixes/ support from Google side. So it is always better to migrate your APIs
Older version of GAM(v1) will also be deprecated at some time but Google hasn't provided any timeline for this. Probably it may take a year(not sure)
Google strongly encourages you to migrate your marketplace application to OAuth2 as soon as possible. Google has already announced deprecation of OAuth1. All top apps on marketplace have migrated their customers to OAuth2 with no issues. We plan to stop allowing installs of OAuth1 applications in near future from the marketplace (specific timelines to be communicated separately).