

Since it is a shared package for many games we have, it is used by many of our players, which makes it challenging to cover all edge scenarios. I’m Seref, Software Engineer at the Core team in InnoGames, and I would like to introduce a new way of testing in-app purchases for iOS games in this blog post.Īt InnoGames, we have an internal payment module as a native iOS package and a native plugin for Unity. In that case, this blog post can help you to make the testing process smoother with StoreKit configuration files. Suppose you ever struggle with testing the payment flow of your iOS game with the Apple sandbox environment.

What if you want to test the “Ask to Buy” feature and you need a child sandbox account? How did you feel when you realize that you cannot invite a sandbox user again if you deleted it accidentally? Have you ever get bored of creating a new email address for every new Apple sandbox account?
