Posts

Post not yet marked as solved
7 Replies
1.3k Views
I have a multiplatform app (not only apple platform) and implemented one license for the app. I have a webserver to make the license available across all the platforms. I use consumable in-apps to implement it. License is bought, added to a webserver and consumed. It's consumable because it should be added to a webserver only once. Everything was fine until now. (1.5 years since initial app release for iOS) Now my app got rejected. According to the app review I use incorrect in-app type. (I disputed that I have multiplatform app but they keep rejecting my app).I understand that if I had a one platform app I would use non-consumable in-apps. But since I already have crossplatform licenses I don't need to have complexity of having a hybrid licensing. As for now licensing is clear to the customers they buy once and use on all platforms. With suggested scheme I will only have non-multiplatform license and will have to confuse people how licensing works.
Posted
by Mobidb.
Last updated
.
Post marked as solved
1 Replies
2.6k Views
I managed to implement apple sign-in and it works fine locally, but when I deploy to a webserver and it make request to token rest api (https://appleid.apple.com/auth/token) I receive {"error":"invalid_client"} 400 error. I run out of ideas what to do with this helpful message.Overall I can say that apple API is not user friendly. At least I would expect error description with more specific information.
Posted
by Mobidb.
Last updated
.