December 15th, 2010 by Arjan Olsder Posted in Analysis & Editorial | No Comments »
A few minutes ago, we were in contact with Gregory Wintengs from Gameloft in Germany as a followup to the billing issues and Gameloft Germany’s response to that toward Golum.
Gregory asked us to remove the original German comments we quoted from Golem and confirmed us that the information was highly inaccurate. The editor from Golem didn’t quote him correctly created the wrong impression about the company and the billing issues. Meanwhile, Gameloft published an official English statement at Android and Me.com.
Gameloft would like to apologize to those who were affected by the following situation on Gameloft’s Android store:
We spotted an issue in our billing process that affected 0.05% of all transactions on our stores in December. After having bought one game through a credit card, some customers were charged a second time under certain circumstances.
All customers who received extra charges will be automatically refunded for all related game charges directly to their credit card accounts, and will receive a free game credit.
This bug has been fixed today.
Again, we sincerely apologize for any inconvenience it might have caused some of our customers. If you need further assistance on Gameloft’s offer for Android please contact: android.support@gameloft.com
Congratulations
Your first AWS Elastic Beanstalk Node.js application is now running on your own dedicated environment in the AWS Cloud
This environment is launched with Elastic Beanstalk Node.js Platform
What’s Next?
- AWS Elastic Beanstalk overview
- AWS Elastic Beanstalk concepts
- Deploy an Express Application to AWS Elastic Beanstalk
- Deploy an Express Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Deploy a Geddy Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Customizing and Configuring a Node.js Container
- Working with Logs
