@william Thanks a lot for your feedback and suggestions! It’s really helpful, and we appreciate you taking the time to share your thoughts.

@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.

Cool - good to hear it. And once again: thanks for reporting it!

Hi @william - thanks for the suggestion - I'll present it to the devs.

One note - when doing custom queries, MongoDB should automatically choose the appropriate index for it -- you shouldn't have to mention it in your query. Thus - adding a custom index for queries that you are finding slow SHOULD pseed them up... (thus your last feature is actually part of the system)