Post

Replies

Boosts

Views

Activity

One auto-renewable subscription always returned in invalidProductIdentifiers while its siblings in the same group resolve
We have three auto-renewable subscriptions in one subscription group. Two resolve normally; the third is always returned in invalidProductIdentifiers. Product A — annual, Approved-previously -> resolves Product B — monthly, Approved -> resolves Product C — monthly, Ready for Review -> NOT returned All three identifiers go out in the same Product.products(for:) / SKProductsRequest call, from the same binary, bundle ID, Sandbox Apple Account and storefront. No error is thrown, C is silently omitted. The only difference is that C has never been approved. Agreements are Active, StoreKit Configuration is None, the storefront is a region where C is enabled, and we have already tried availability changes, level changes, status changes, sandbox re-login and reinstalls over 24+ hours. Is a subscription that has never been approved expected to be unfetchable in the sandbox? The documentation suggests the opposite. And if approval is the prerequisite, is there a path that doesn't require waiting for our in-flight app version to clear review? Full details, screenshots and logs: FB23978472
1
0
70
2h
One auto-renewable subscription always returned in invalidProductIdentifiers while its siblings in the same group resolve
We have three auto-renewable subscriptions in one subscription group. Two resolve normally; the third is always returned in invalidProductIdentifiers. Product A — annual, Approved-previously -> resolves Product B — monthly, Approved -> resolves Product C — monthly, Ready for Review -> NOT returned All three identifiers go out in the same Product.products(for:) / SKProductsRequest call, from the same binary, bundle ID, Sandbox Apple Account and storefront. No error is thrown, C is silently omitted. The only difference is that C has never been approved. Agreements are Active, StoreKit Configuration is None, the storefront is a region where C is enabled, and we have already tried availability changes, level changes, status changes, sandbox re-login and reinstalls over 24+ hours. Is a subscription that has never been approved expected to be unfetchable in the sandbox? The documentation suggests the opposite. And if approval is the prerequisite, is there a path that doesn't require waiting for our in-flight app version to clear review? Full details, screenshots and logs: FB23978472
Replies
1
Boosts
0
Views
70
Activity
2h