The inAppPurchasePriceSchedules payload example seems wrong.
The example is also different from the API specification..
In my environment, it worked with the following contents.
(The values are changed according to the example.)
{
"data": {
"type": "inAppPurchasePriceSchedules",
"relationships": {
"inAppPurchase": {
"data": {
"type": "inAppPurchases",
"id": "6446452615"
}
},
"manualPrices": {
"data": [
{
"type": "inAppPurchasePrices",
"id": "ABCDSJOFDSFJDSI"
}]
}
}
},
"included": [
{
"type": "inAppPurchasePrices",
"id": "ABCDEFGHIJKL",
"attributes": {
"startDate": null
},
"relationships": {
"inAppPurchaseV2": {
"data": {
"type": "inAppPurchases",
"id": "6446452615"
}
},
"inAppPurchasePricePoint": {
"data": {
"type": "inAppPurchasePricePoints",
"id": "NjQ0NjQ1MjYxNV91c181"
}
}
}
}]
}
Also, in setting the initial prices, the inAppPurchasePrices id was required but had no meaning.
Works with any value, eg "ABCDEFGHIJKL".
And Apple ignores the "ABCDEFGHIJKL" and gives inAppPurchasePrices an ID like "eyJpIjoiMTYzNzYwN.....".
shougayugokugoku
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for