Samsung deeply values the global network of employees at all of our manufacturing facilities who make it possible for us to deliver our products to our
Testing your in-app subscriptions is a critical step in ensuring you’re offering
your customers a high quality service.
In order to make testing easier and faster, starting on February
20th, we are introducing shorter renewal intervals for test purchases
made with license-test accounts. Currently, subscriptions by license-test
accounts renew daily. The new changes will allow you to test an entire
subscription cycle, including 6 renewals, in under an hour. We will also be
shortening the testing time intervals of features such as grace period and
Please be aware that these changes are coming so you can update your testing
flows accordingly prior to the change. Also note that existing test
subscriptions still active on February 20, 2018 will automatically be canceled
at that time.
Renewal times will vary based on the subscription period:
|Subscription period||Test subscription period|
|1 week||5 minutes|
|1 month||5 minutes|
|3 month||10 minutes|
|6 month||15 minutes|
|1 year||30 minutes|
Time intervals of the following features will also be shortened for test
|Free trial||3 minutes|
|Introductory price period||Same as test subscription period|
|Grace period (both 3 and 7 day)||5 minutes|
|Account hold||10 minutes|
Note: These times are approximate; you may see some small
variations in the precise time of an event. To compensate for variation, call
Play Developer API to view current status after every subscription
Due to the increase in renewal frequency, the number of renewals is limited to 6
regular renewals (not including intro price/free trial). After 6 renewals, the
subscription will be automatically canceled.
Here are several examples of how the new renewal times are applied.
Don’t forget to check the Testing
In-app Billing page for more details on testing your subscriptions. If you
still have questions, reach out through the comments or post your question on Stackoverflow using the tag google-play.
Posted by Kacey Fahey, Developer Marketing, Google Play
Kicking off the new year, we’re excited to welcome our latest group of Android Excellence apps and games. These awardees represent some of the best experiences and top performing apps and games on the Play Store and can be found with other great selections on the Editors’ Choice page.
If you’re looking for some new apps, below are a few highlights.
- EyeEm: A great photo editor app with a full suite of filters and tools to make your pictures shine. Learn style tips from their community and even sell your images through the EyeEm marketplace.
- Musixmatch: Check out Musixmatch’s updated app while learning the lyrics to all your favorite songs. The app is compatible with many of the top music streaming services and you can even follow along with your Android Wear device or on the big screen with Chromecast support.
- ViewRanger: Plan your next hiking adventure by discovering new routes and trail guides with ViewRanger. Check out the Skyline feature using your phone’s camera to identify over 9 million sites across the world through augmented reality.
Here are a few of our favorite new games joining the collection.
- Fire Emblem Heroes: Nintendo’s popular strategy-RPG franchise is now reimagined for mobile. Fight battles, develop your heroes’ skills, and try various gameplay modes for hours of exciting gameplay.
- Lumino City: Explore the charming papercraft style world in this award-winning puzzle adventure game. The beautiful scenery is all handcrafted.
- Old Man’s Journey: Gorgeous scenery, an immersive soundtrack, and deep emotion help you uncover the old man’s life stories while you solve puzzles and shape the landscape to determine his future.
Congratulations to the newly added Android Excellence apps and games.
|New Android Excellence apps||New Android Excellence games|
How useful did you find this blogpost?
It’s right around the corner… Cisco Live Europe 2018 in Barcelona, and I absolutely can’t wait! Every Cisco Live I’ve ever been to, or presented at, has been an amazing experience, but Barcelona is going to be in a league of its own. From the moment I arrive in Spain on Friday morning the entire […]
The Internet of Things – the increasingly connected world in which we live – is rapidly expanding. We love our convenient and fun devices – like personal assistants, wearables, speakers, cameras, TVs, cars, home alarm systems, toys and appliances. But it’s important to understand that connected devices rely on information about us – such as […]
Since then, there’s been considerable discussion about what this means for Google Cloud and the industry at large. Today, we’d like to clear up some confusion and highlight several key considerations for our customers.
What are “Spectre” and “Meltdown”?
Independent researchers separately discovered and named these vulnerabilities “Spectre” and “Meltdown.”
Project Zero described three variants of this new class of speculative execution attack. Variant 1 and Variant 2 have been referred to as “Spectre.” Variant 3 has been referred to as “Meltdown.” Most vendors are referring to them by Common Vulnerabilities and Exposures aka “CVE” labels, which are an industry standard way of identifying vulnerabilities.
There’s no single fix for all three attack variants; each requires protection individually.
Here’s an overview of each variant:
Variant 2 (CVE-2017-5715), “branch target injection.” This variant may either be fixed by a CPU microcode update from the CPU vendor, or by applying a software protection called “Retpoline” to binaries where concern about information leakage is present. This variant is currently the basis for concern around Cloud Virtualization and “Hypervisor Bypass” concerns that affect entire systems.
Variant 3 (CVE-2017-5754), “rogue data cache load.” This variant is the basis behind the discussion around “KPTI,” or “Kernel Page Table Isolation.” When an attacker already has the ability to run code on a system, they can access memory which they do not have permission to access.
For more information on these variants, please read this week’s Google Security post.
Am I protected from Spectre and Meltdown?
Google’s engineering teams began working to protect our customers from these vulnerabilities upon our learning of them in June 2017. We applied solutions across the entire suite of Google products, and we collaborated with the industry at large to help protect users across the web.
G Suite and Google Cloud Platform (GCP) are updated to protect against all known attack vectors. Some customers may worry that they have not been protected since they were not asked to reboot their instance. Google Cloud is architected in a manner that enables us to update the environment while providing operational continuity for our customers. Via live migration we can patch our infrastructure without requiring customers to reboot their instances.
Customers who use their own operating systems with Google Cloud services should continue to follow security best practices and apply security updates to their images just as they would for any other operating system vulnerability. We’re providing an up-to-date reference on the availability of vendor patches for common operating systems on our GCE Security Bulletin page.
I’ve heard that Spectre is nearly impossible to protect against. Is this true?
There has been significant concern in particular about “Spectre.” The use of the name “Spectre” to refer to both Variants 1 and 2 has caused some confusion over whether it’s “fixed” or not.
Google Cloud instances are protected against all known inter-VM attacks, regardless of the patch status of the guest environments, and attackers do not have access to any customers’ data as a result of these vulnerabilities. Google Cloud and other public clouds use virtualization technology to isolate neighboring customer workloads. A virtualization component known as a hypervisor connects the physical machine to virtual machines. This hypervisor can be updated to address Variant 2 threats. Google Cloud has updated its hypervisor using “Retpoline,” which addresses all currently known Variant 2 attack methods.
Variant 1 is the basis behind claims that Spectre is nearly impossible to protect against. The difficulty is that Variant 1 affects individual software binaries, so it must be handled by discovering and addressing exploits within each binary.
Risks that Variant 1 would pose to the infrastructure underpinning Google Cloud are addressed by the multiple security controls that make up our layered “defense in depth” security posture. Because Google is in full control of our infrastructure from the hardware up to our secure software development practices, our infrastructure is protected against Variant 1. You can read more about the security foundations of our infrastructure in our whitepaper.
We work continuously to stay ahead of the constantly-evolving threat landscape and will continue to roll out additional protections to address potential risks.
As a user of the public cloud, am I more vulnerable to Spectre and Meltdown than others?
In many respects, public cloud users are better-protected from security vulnerabilities than are users of traditional datacenter-hosted applications. Security best practices rely on discovering vulnerabilities early, and patching them promptly and completely. Each of these activities is aided by the scale and automation that top public cloud providers can offer — for example, few companies maintain a several-hundred-person security research team to find vulnerabilities and patch them before they’re discovered by others or disclosed. Having the ability to update millions of servers in days, without causing user disruption or requiring maintenance windows, is difficult technology to develop but it allows patches and updates to be deployed quickly after they become available, and without user disruption that can damage productivity.
Spectre and Meltdown are new and troubling vulnerabilities, but it’s important to remember that there are many different types of threats that Google (and other cloud providers) protect against every single day. Google’s cloud infrastructure doesn’t rely on any single technology to make it secure. Our stack builds security through progressive layers that deliver defense in depth. From the physical premises to the purpose-built servers, networking equipment, and custom security chips to the low-level software stack running on every machine, our entire hardware infrastructure is Google-controlled, -secured, -built and -hardened.
Is performance impacted?
On most of Google’s workloads, including our cloud infrastructure, we’ve seen negligible impact on performance after applying remediations. This was explained further in our follow-up Security blog post on January 4.
There are many conflicting reports about patch impacts being publicly discussed. In some cases, people have published results of tests that focus solely on making API calls to the operating system, which does not represent the real-world scenario that customer software will encounter. There’s no substitute for testing to determine for yourself what performance you can expect in your actual situation. We believe solutions exist that introduce minimal performance impact, and expect such techniques will be adopted by software vendors over time. We designed and tested our mitigations for this issue to have minimal performance impact, and the rollout has been uneventful.
Where can I get additional information?
Technical details from Project Zero about these vulnerabilities
Information about these vulnerabilities and mitigations across all Google products
Additional information about impacts to performance
Our Support page offers a list of affected Google products and will be updated with their current status of mitigation against these risks
Our GCP Security Bulletins page will provide notifications as other operating system maintainers publish patches for this vulnerability and as Compute Engine releases updated OS images
Today, Talos is publishing a glimpse into the most prevalent threats we’ve observed between December 29 and January 05. As with previous round-ups, this post isn’t meant to be an in-depth analysis. Instead, this post will summarize the threats we’ve observed by highlighting key behavior characteristics, indicators of compromise, and how our customers are automatically […]