# Subscription Pitfall

DevFeed: [Subscription Pitfall](<https://devfeed.tech/articles/subscription-pitfall-19536.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/subscription-pitfall/>)

Author: Shai Almog

Published: 2018-11-05T00:00:00Z

Content type: opinion

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [post](<https://devfeed.tech/tags/post.md>), [subscription](<https://devfeed.tech/tags/subscription.md>), [update](<https://devfeed.tech/tags/update.md>)

## AI overview

The article describes a pitfall when implementing auto-renewing in-app subscriptions. The author found that subscribe(sku) did not work with the receipt API and was expected to be deprecated, while a later note says developers should use subscribe for subscriptions again.

## Source excerpt

A while back Steve wrote about auto-renewing subscriptions and I recently got a chance to implement such a subscription in an app. However, it seems that all the changes in the world of in-app purchase created a situation where API's work in some cases and don't work for all of them. __ After publishing this post we walked back on this, you now need to use subscribe for subscriptions again! In the blog post, Steve used the purchase(sku) API to subscribe. This worked correctly as subscriptions are determined by the respective app store. As I implemented this code I chose to use the subscribe(sku) method which seems to make more sense. Unfortunately it doesn't work and would be deprecated with the update this Friday.