@Paul-Winterhalder Now, purchase validation proceeds normally regardless of the “Use App Store Server API for legacy receipts (optional)” option setting.

@Paul-Winterhalder Yes, that’s correct. It is a sandbox account.

After the patch, it would be good if existing receipts continue to work by default.

@Paul-Winterhalder

Hello

Project 14594
Tester ID 1b5c9fce-a890-4d86-86aa-dd71263d0fc1

App Store \Server API has been fully configured in the current BrainCloud settings, and “Use App Store Server API for legacy receipts (optional)” is turned OFF.
This option must be disabled for the legacy receipt flow to function, so it is intentionally kept turned off in order to use the current setup.

When checking Verify Purchase in the user ID logs, the client has not yet been updated, so it is not sending a transactionId and is instead sending the receipt, following the legacy receipt-based flow.

@Michael-Costa

"packetId": 13,
"responses": [
{
"data": {
"resultCode": 101,
"errorMessage": "Transaction id not found.",
"store": "itunes"
},
"status": 200
}
]
}

After configuring the App Store Server API, enabling “Use App Store Server API for legacy receipts (optional)” appears to cause legacy receipt validation to stop working. Instead, the system starts requiring a transaction ID.

In other words, checking it has the opposite effect.

We are currently running a live service using the existing receipt-based flow, so we have this option turned off—meaning we are effectively using it in practice (because enabling it breaks legacy). We are very concerned that if this behavior gets “fixed” later, it could cause issues in our live service. Please take this into account and ensure any patch/change does not introduce regressions for live operations.

@Paul-Winterhalder Hello, is there guide for this menu?

and what is "Use App Store Server API for legacy receipts (optional)"?

https://discussions.unity.com/t/unity-iap-5-0-2-ios-sandbox-same-receipt-returned-for-all-purchases-after-the-first-one/1692048/5

Due to the issue described in the Unity discussion above, we need StoreKit 2 support on iOS as soon as possible. Please prioritize StoreKit 2 integration

Hi @Paul-Winterhalder

I wanted to follow up regarding StoreKit 2 JWS receipt support.
At the moment, Unity IAP v5 relies on StoreKit 2 by default, but there are two major issues we’re facing in production:

VerifyPurchase currently only supports StoreKit 1’s PKCS#7 receipt format.
When StoreKit 2 is used (as in Unity IAP v5), the App Store often returns empty receipts in certain environments — especially on Apple Silicon (M-series) Macs running iPadOS compatibility mode — causing verification to fail and users to lose their purchases.

In addition, Unity IAP v5 has a known issue where after the first successful purchase, all subsequent purchases return the same receipt as the first transaction.
This makes it impossible for the server to distinguish or validate new purchases, since every transaction reuses the initial receipt data.

Both of these problems make proper validation impossible under StoreKit 2, and they directly affect live monetization and user trust.

If StoreKit 2 JWS receipt support could be prioritized or exposed as a secondary endpoint (for example, itunes2), it would help developers transition more safely.
Given the impact, we would really appreciate if this work could be accelerated.

Applied in version 5.6. Thank you.

@JasonL This is what I'm already doing, which is why I'm requesting a new feature, as it has the drawbacks listed above.

Looking at it again, I see you added time correction. I'll try it.

Currently, we are repeating push notifications by scheduling cloud codes 24 hours later with push notifications to repeat them at a set time every day for a specific segment.

The problem with this method is that the time gradually gets later due to server delays.

Also, there was an issue a while ago where calls were suddenly made at a time other than 24 hours due to a server error.

It would be nice to have a function that can repeat at a set time (UTC) rather than after N hours.

yes that reason too. readgroup result data is not enough so need more data(like score) so need.

it will be better if leaderboard page have refresh button.

it is really hard to see data check in same leaderboard.
for now, we must change to other page or other leaderboard to see current leaderboard's lates data.

When I have a random list of groups, I want to get the ranking information of those groups.

We need the function to get multiple groups's scores on the same group leaderboard. Like GetPlayersSocialLeaderboard

In many RPG games, a single account can have multiple characters (or multiple channels).

Our game studio has recently received support through the Custom Entity feature, allowing users to have multiple unique nicknames.

Through this feature, we have partially succeeded in implementing the ability to have multiple characters, but in features such as the leaderboard and group functionalities, it still operates on an account basis.

Nowadays, many mobile games are creating numerous channels, allowing players to create characters on each channel. Each channel has its own independent purchase history, leaderboard, guild, and play data.

This approach helps extend the game's lifespan and motivates new players. Are there any plans to implement this feature?

Thank you.

Hello. The Apple App Store posted the following notice. Has anything been done about it?

Thank you so much!

still exist for new

and other places ( tournament templetes etc.)

in notification templete