Twitter | Search | |
Peter Steinberger
What's the process of testing subscriptions on the Mac App Store? Does this ever work or do we keep on testing live + iterating fast? (Sandboxed release)
Reply Retweet Like More
Ilja A. Iwas Nov 11
Replying to @steipete
We were thinking about returning to the MAS with a subscription plan only (regular licenses are too much of a pain when it comes to paid upgrades on MAS). But broken processes like this are keeping me from even trying. 🙁
Reply Retweet Like
Peter Steinberger Nov 11
Replying to @iljawascoding
We basically test live or with compiled variants.
Reply Retweet Like
Jamie Birch Nov 12
Replying to @steipete
I had this exact error myself, although I was only testing non-consumable IAPs (not subscriptions). I did solve it (see issue), but the solution was exasperating given the vague error message. Not sure whether it applies in your case, but good luck.
Reply Retweet Like
Jamie Birch Nov 12
Replying to @steipete
I should add my post-mortem thought that it may be “bad luck” to re-use a sandbox tester that has already been ‘spoiled’ by making iOS App Store purchases. Try making a whole new one just for macOS App Store purchases.
Reply Retweet Like
Steve Tibbett Nov 11
Replying to @steipete @RevenueCat
I'm considering just so it's someone else's problem.
Reply Retweet Like
Peter Steinberger Nov 11
Replying to @stevex @RevenueCat
We use them - still want to test this.
Reply Retweet Like
BJ Homer Nov 11
Replying to @steipete
I believe you need to use a sandbox test user, which you can set up in AppStoreConnect. Haven’t actually run through this in a while though.
Reply Retweet Like
Andreas Monitzer Nov 11
Replying to @steipete
Some situations can’t be tested on the sandbox anyways, testing in production is the only way for in-app-purchases. I had a product that worked fine in the sandbox but broke 90% of the time on the live server.
Reply Retweet Like