hi. @JasonL
This is somewhat different from what I had in mind.
While bundling and using it is a viable option,
it differs somewhat from the goal of "dynamically distributing a single item at once."
Bundles require pre-composition and require version control. Furthermore, the actual disbursement only occurs after the bundle is opened.
A function like AwardUserItem (multi defIds) is required.

We're using ExternalAuth,
and extending the session through Reconnect in scenarios where the session is disconnected.
The problem is that anonymous logins continue to accumulate in Credentials.
Is this the intended behavior?

hi, @JasonL any update?

hi. @JasonL

Thank you for your reply.
I thought it was a JavaScript object, so I used Object.Assign({}, session), JSON.Parse(JSON.stringify(session)).
I tried to copy the object and use it, but since it's a reference to a Java object, it didn't work as intended.
Please help me retrieve the necessary data.

We use the S2S script to check whether the player's session is valid based on the sessionId and profileId sent from the client.

GetSessionForSessionIdAndProfileId

We use this function, and when accessing the returned field,

the isLoggedOut field, we receive a Java access restriction error.

We use this function closely in an S2S environment and check the session for every API call, so we need to use this field to determine whether the session has been invalidated (logged out, etc.).

If there is no problem, please allow access to that field.

We subscribed to the dev plus plan.
Go live with your project! When you press the button, a rate plan conversion window will appear.

In the case of go live, I would like to inquire whether it is provided starting from the lite rate.

StoreKit2 needs immediate support.

Hello.

I'd like to ask about some inefficiencies in the user inventory.

1. Item rewards should be called individually, not in bulk.
2. To find items based on their 'defId' within the inventory, a full search is required.

For itemCatalogs, which can only hold one item, we need to check if the item exists in the user's inventory before issuing the reward.
The problem is that it only supports itemId-based verification.

Furthermore, since there's no bulk-based reward payment system, rewards must be paid out individually. However, setting up approximately 100 to 200 items initially...

results in inefficient code.