brainCloud

Hi folks,

The 4.5.5 release is feature-complete and set to be deployed on Tuesday, July 14th.

Important notes:

• The upgrade will happen between the hours of 8am - noon Eastern Time
• During this time the Design Portal will be disabled. Apologies for the inconvenience!
• All API Services will continue to be available throughout the upgrade
• You can subscribe to service status notifications here - https://braincloud.statuspage.io

A quick summary of 4.5.5 features:

• Amazon In-app Purchases
• Global Files V3 Portal & Deployment Support
• Slack Alerts!
• Custom Entity Singleton API
• Auto-Delete Dormant Users
• Leaderboard Deployment Options
• Custom Entity Deletion Queries
• Product & Promotion Management APIs
• Segment, Currency and Notification Queries
• RTT reliability improvements
• Relay Server client library improvements (especially in the Java libs)
• Improved Room & Relay Server launches
• Misc. fixes and performance enhancements

You will find the full details in the 4.5.5 release notes:
https://getbraincloud.com/apidocs/release-4-5-5/

Feedback welcome!

Paul.

Hi Lee,

Apologies for the issue.

As you mention - it appears that the issue was due to a Redis failure - and some fail-over handling in our API Servers that didn't seem to work properly for all servers. This resulted in some RTT errors for some apps.

The issue has since been addressed (by rebooting the failing servers).

We're going to do a post-mortem on the Redis fail-over code to see if we can find the offending code-path - and we've added additional monitoring alerts that will look for just this sort of error in the future so that we can act upon it immediately.

Thanks for reporting it!

Paul.

Hi Chad,

We'll look into it. There are structural complications - in that we keep a separate queue of players waiting to join each type of lobby... so you're looking at in this case changing it to a global (or filterable) queue of waiting players... we'll have to think on that.

I'm assuming that the team and min:max counts for the various lobby types differ? Cause if they don't, you could have a single lobby type - which lobby info that determines the type of game.

Would that be an option for you?

Paul.

Hi @Ali-Raza ,

They were added in brainCloud 4.4:

• SysUpdatePropertyJson() - https://getbraincloud.com/apidocs/apiref/?objective_c#capi-globalapp-sysupdatepropertyjson
• SysUpdatePropertyString() - https://getbraincloud.com/apidocs/apiref/?objective_c#capi-globalapp-sysupdatepropertystring

Hope that helps!

Paul.

Hi @Ali-Raza ,

Actually I have good news - we added that API to 4.4!

These two methods are available to you now:

• SysUpdatePropertyJson() - http://getbraincloud.com/apidocs/apiref/#capi-globalapp-sysupdatepropertyjson
• SysUpdatePropertyString() - http://getbraincloud.com/apidocs/apiref/#capi-globalapp-sysupdatepropertyjson

I guess we should have publicized their addition more!

Hope that helps!

Paul.

Hi folks,

Our planned 4.6 release was getting too big - so we're splitting it into 4.55 and 4.6.

The 4.55 release should arrive within the next 30 days.

The big headliner feature is at long last, brainCloud will support Amazon In-app Purchases !

There are also a bunch of useful API additions. Check out the details on our Roadmap.

The bad news is that Cloud Code Folder are still planned for 4.6 - which is going to be a bit longer. That said, we're working hard to get it right!

Cheers,

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.

Hi Bigzer,

We aren't aware of any issues running our javascript client lib under Edge - and haven't been able to repro your issue.

I'm not a javascript guy - but I'm noticing other warnings / errors there - do those also happen in Chrome?

Paul.

Ah - indeed @Carson-Herrick , you are correct.

Turns out "bchosting" is the name of the group we use in our repo example. braincloudhost is indeed the correct user name.

Apologies for the confusion!

Paul.

Hi @Carson-Herrick ,

You set the permissions in Dockerhub - it's the repository we will retrieve your custom image from.

In summary, you need to do the following in Dockerhub:

1. Create a team, called "brainCloud" probably, that you are going to use to give us access.
2. Invite our user, braincloudhost to your repo, and place us on that brainCloud Team. (Note - this user still has no permissions in your repo)
3. Go to the image that you want to share, then the permissions tab, and give the "brainCloud" team read-only access to that image.

If you do this properly, our braincloudhost user will have read-only access to that image, and nothing else.

I hope that helps!

Paul.

Edit - fixed step 2 with the correct user name, braincloudhost... (I had mistakenly said "bchosting")