Skip to main content

2 posts tagged with "ios"

View All Tags

· 3 min read

If you’re an app developer or someone managing in-app purchases, you may have recently seen a warning about the SHA-1 intermediate certificate used for signing App Store receipts expiring on January 24, 2025. Apple’s notice has caused some concern, especially for those who rely on on-device receipt validation. But don’t worry—if you’re using IAPHUB to manage your in-app purchases, you’re already covered.

What’s Happening with the SHA-1 Intermediate Certificate?

The SHA-1 intermediate certificate used by Apple for signing App Store receipts will expire on January 24, 2025. This has prompted many developers to assess whether their app's receipt validation process will continue to work seamlessly after this date. The key concern is that if you're still using the SHA-1 certificate for on-device receipt validation, your app might face issues when the certificate expires.

This is an important change, but there’s no need to panic if you're using IAPHUB. IAPHUB validates all receipts on the server-side by using the official Apple API, which means you’re always using the most up-to-date certificates and validation processes.

Why You Don’t Need to Worry with IAPHUB

At IAPHUB, we understand the complexities of receipt validation. We handle the technicalities for you, so you don’t have to. IAPHUB performs receipt validation on the server using Apple's official APIs, ensuring that your receipts are always validated correctly and securely.

When Apple switches to the new SHA-256 intermediate certificate, our server-side validation will seamlessly support the update, ensuring uninterrupted validation for your users. You can rest assured that IAPHUB has already taken care of the necessary adjustments.

No Action Needed on Your Part

For IAPHUB users, this update doesn’t require any changes to your app or your implementation. Unlike on-device validation, which may require updates to support SHA-256, our server-side receipt validation automatically handles these updates. You can continue to rely on IAPHUB to ensure your app’s in-app purchase validation process remains flawless, regardless of Apple's changes.

What About Developers Who Aren’t Using IAPHUB?

If you're not using IAPHUB, you may need to review your receipt validation process. Apple’s move to SHA-256 will require updates to ensure your app continues validating receipts properly after January 24, 2025. Developers who use on-device validation will need to ensure their app can handle the new intermediate certificate to prevent potential issues.

Conclusion

If you're using IAPHUB, you can rest easy knowing that the upcoming expiration of the SHA-1 intermediate certificate won’t affect your app. Our server-side receipt validation seamlessly supports the transition to SHA-256, so there’s nothing you need to do. IAPHUB ensures your in-app purchase validation process remains uninterrupted, allowing you to focus on growing your app rather than worrying about certificate changes.

Ready to future-proof your in-app purchase system and eliminate receipt validation concerns? Sign up for IAPHUB today and experience seamless, hassle-free validation!

· 2 min read

Exciting news: IAPHUB has rolled out full support for StoreKit V2 on iOS 15 and above! 🚀📱

As you may know, IAPHUB uses Apple's StoreKit SDK under the hood to process your in-app purchases. While the previous version, StoreKit SDK (V1), has served its purpose, it also encountered several issues that Apple sought to address with the release of StoreKit V2.

And let me tell you, a lot has changed! Normally, upgrading your codebase to StoreKit V2 would be quite the undertaking. However, since you're leveraging IAPHUB, we've handled all the heavy lifting for you, ensuring a seamless transition without any noticeable differences on your end!

One of the standout features of StoreKit V2 is that Apple now returns the price and currency of a transaction when validating a purchase using their server API (you might not have been aware, but this wasn't the case before). This means no more reliance on client-side data, resulting in more accurate and transparent in-app purchases than ever before. Moreover, it's expected to be faster and more reliable, providing a smoother experience for both you and your users.

And rest assured, even if some of your users haven't made the leap to iOS 15 yet, IAPHUB has got you covered. We seamlessly transition to StoreKit V1 for iOS versions below 15, ensuring uninterrupted functionality for all users.

Before you begin, don't forget to configure the App Store Server API.
Update the IAPHUB SDK to the latest version, then simply set enableStorekitV2 to true when initializing the IAPHUB SDK using the start method. IAPHUB will automatically use StoreKit V2 if it's available.

Also, make sure to test a few transactions in the sandbox before rolling out your app update with StoreKit V2. Proper testing before publishing a change is always a good idea 🙂. Happy coding!