What is the significance of an App Store Server Notification that has no signedTransactionInfo?

Question

Created Oct ’22

Replies 6

Boosts 0

Views 1.9k

Participants 7

We have an App Store Server Notification endpoint. Our app offers an in app subscription. Most notifications have all of the expected fields, but in a small number of cases the decoded signedTransactionInfo and signedRenewalInfo fields are empty.

I can't see anything about these fields being optional in the documentation, and without the transaction information I can't get the transaction id of the user, so I can't tell how this notification relates to others for the same original transaction id.

Are these notifications expected? Should I be handling them in a special way? Or should I just ignore them?

For example, a normal transaction will have the following fields:

responseBodyV2DecodedPayload (
    [notificationType] => DID_RENEW
    [notificationUUID] => …
    [version] => 2.0
    [signedDate] => 1660947328849
    [data] => (
            [bundleId] => com.playpokpok.playroom
            [bundleVersion] => 9
            [environment] => Sandbox
            [signedTransactionInfo] => JWSTransactionInfo
            [signedRenewalInfo] => JWSRenewalInfo
        )
)

But one of these unexpected requests will have the following form:

responseBodyV2DecodedPayload (
    [notificationType] => EXPIRED
    [subtype] => VOLUNTARY
    [notificationUUID] => …
    [version] => 2.0
    [signedDate] => 1662661854606
    [data] => (
            [appAppleId] => 1550204730
            [bundleId] => com.playpokpok.playroom
            [bundleVersion] => 6
            [environment] => Production
        )
)

Boost

Answer 1

App Store Commerce Engineer OP

Apple

Oct ’22

Could you provide examples and your account/app details in a ticket and reply with the FB#? https://developer.apple.com/forums/thread/718656

0

Answer 2

PatrickRogers OP

Oct ’22

I filed feedback ticket FB11720914 with the requested information, including the raw notification data that was sent from the server.

1

Answer 3

DanSnoop OP

Jan ’23

Did this ever reach any conclusion?

I ask, as my organization is currently experiencing the same issue i.e. a small number of notifications that are missing either the signedTransactionInfo or signedRenewalInfo. There appears to be nothing systematic in the type of notifications. I've seen examples for a variety of notification types (e.g. renewal, expiry, cancellation etc)

Kind regards

Dan Poxton

0

Answer 4

Exilz OP

Jan ’23

Same issue here. We've switched to apple notifications v2 for months now and suddenly we've noticed both transactionInfo and renewalInfo randomly missing for a few days now.

Our system is built so that it assumes that all events include these properties, which has always been true until now. Did something change in the way notifications work? We now have to drop some of them, because we're missing critical information that let us update our database.

0

Answer 5

Exilz OP

Jan ’23

Somehow, this stopped happening on January 15 2023. Go figure...

0

Answer 6

gogi6061 OP

Oct ’23

Hello! Still have this problem with null signedTransactionInfo. Two requests without this field. Is there any news?

0