Thank you, fantastic. I appreciate all the information you have given.

Hello @Gavin-Beard!

We've had trouble reproducing this issue on our end. After some testing with a small app on MacOS and iOS, we have not been able to see the error you are encountering using Unity 2021.3.8.

If you could, please check out the app here and let us know if this issue is still persisting. It is a barebones authentication app and it should run on multiple devices. The Authentication.cs script has all the gory details. Just open up the Main scene under Assets > App > Misc > Main.unity to get it running. You will also need to add your brainCloud credentials, but you can copy the Authentication example template in brainCloud to test the app.

Please let us know how this app works on your end and if any issues are encountered! You should be able to click on any error logs in the in-app console to copy the log to your device's clipboard.

As for your specific issue, my best guess is that perhaps an external library of sorts might not be supported with brainCloud, such as the Newtonsoft Json.NET library. For JSON de/serializing, brainCloud comes with JsonFX. You can also make use of Unity's own JsonUtility for structured JSON de/serialization. Both the app I've shared and the examples on our GitHub make use of JsonFX extensively.

If you'd like to know more and see how a more robust app can handle brainCloud authentication, as Franco suggested, you should check out our Authentication example on our Unity Examples GitHub.

Hope this helps! Please let us know if you have further questions or inquiries about this.

These points above are indeed good examples regarding "forcing bad practices":

If I have 3 free API calls after the API call, after the 3rd freebie, I can return it and call again for 1 core + 3 more that can branch off again. This is inefficient for BC, yet beneficial for end-users (thus, forcing bad practices since it costs and gives more if we avoid the pre and post hooks).

If a workaround to save API costs would be more work for the user, and costs more for BC, that's a lose-lose. If such a "hole" exists, shouldn't it be repriced for that consideration to make it the win-win you folks want it to be?

@JasonL
Thank you!!

Hi Chris,

User entities are primarily indexed by profileId + entityType - so the singleton API will scale well no matter how many players you have.

That said, if your use case gets more complicated, with say hundreds of entities of a particular type per user (say maybe you are modelling user created towns, that sort of thing) - you could consider using Owned Custom Entities instead. You can define addition, custom indexes for those... keeps those lookups fast and efficient.

In addition, if you end up having >1000 Global Entities, you should definitely look at switching to Unowned Custom Entities. Same deal - you can define your own custom indexes...

Hope that helps!

Paul.

Hi @Alexandru ,

We've just officially added the Segment call you're looking for to brainCloud 4.55 - which is targeted for release in the next ~30 days...

Updated Roadmap here - https://portal.productboard.com/braincloud/1-braincloud-baas-roadmap

Paul.

@JasonL I understand the reason, but please do provide a way to pass custom data to authenticate api so we can use that data to set user displayname or profile picture or soemthing else on post-hook.
Without this, we have no choice but to call a seperate call from client (so no beneift of 2 free api inside cloud call)

No problem - happy to help!

Paul.

Happy to help! 👍

@paul-winterhalder
then it can repeat push notice?

Thanks guys! I figured it would be ridiculous if I had to do timeout checks and retries myself 🙂

Follow-up on this...

My guys have looked into it, and the way we version our global files isn't compatible with this new feature from Unity. Apologies!

(PS - No plans yet for when/if we'll support it. Certainly tons of folks use an external CDN with brainCloud apps though - so the option is still there for you!)

Happy to help! 🙂

Paul.

Posting a copy of the AWS service health page for posterity.

It mostly refers to the outage impacting DynamoDB - but a lot more services than that were impacted. We expect that just means that a lot of AWS services use DynamoDB under-the-covers to operate.

2025-10-20_05-58-47.png

Ok, I found it. It wasn't a global setting, it was a filter on the reports. Thanks!

HI @richard - we're currently working on a feature that will handle this directly for brainCloud 5.9.

In the meantime, an interim approach would be to:

Manage the Lives in a virtual currency. In the item catalog - you can indicate the currencies to award from the offer via the extra data JSON. And create a post-hook on PurchaseUserItem - calling a script to award the appropriate currencies - and immediately consume the new "item" that was purchased...

Just a thought...

[But yeah - we're going to have a more direct solution in 5.9 - which is currently targeted for November release.]

Paul.

My view is that there should be a "guaranteed service availability" at the time of purchase not unlike buying an appliance with a year warranty..

Pull the game from stores and let the remaining players enjoy the sunset.
Of course it's not always as simple as "just keep the lights on longer" but a guaranteed period of availability which is tied to new purchases should be in your plans before your service ever reaches the public, rather than hoping to grab as much money as possible before dumping it and throwing the consumer under the bus.

Okay - cool!

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

You are welcome. Thanks for the suggestion!