As a further heads up folks - it is looking like the 4.5.6 server release may get delayed until early next week. This is to allow us to create a proper mechanism for controlling with specific versions of Lobby Services are active at a time... (right now, it is possible for both old and new lobby services to be active during an upgrade transition - and given how much lobby processing has changed in this release - that wouldn't be good). That said - the rest of 4.5.6 is ready - so we are going to be doing a bit of an incremental roll-out... We are starting to release the 4.5.6 Client Libraries today We are also making the 4.5.6 Relay Servers available (on our existing 4.5.5 servers) <- this is a simple feature gate for us to enable. Then, once the 4.5.6 servers (with the new Lobby Servers and a few other fixes) are available, we will release them... that should be either late this week, or more likely early next week). Anyway, just FYI... 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)

Also getting the same error with "Sign In With Apple" when using the brainCloudWrapper.AuthenticateApple() method

To limit operations like IncrementExperiencePoints() to cloud code only. This will essentially take away the ability to make these calls from the bare client API. You can see a script that enforces these restrictions here - https://getbraincloud.com/apidocs/cloud-code-central/handy-cloud-code-scripts/restrictclientcalls-script/ Refer to another post below for more strategies you can apply to prevent cheating: https://forums.getbraincloud.com/topic/23/discussion-strategies-to-prevent-cheating-in-tournaments

Amazing, especially Amazon In-Apps support

@JasonL I can confirm they are working despite a warning, in strict mode. Thanks!

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.

@Paul-Winterhalder said in Matchmaking: Search Multiple Lobby Types: that Thanks Paul, I don't think I could do the different lobby info option as I would like the players to choose specifically which game mode and if I understand correctly, I can only do that by having the players search for a lobby of that game mode. It's not too much of an urgent issue, I just wanted to put it out there and see how realistic it was. I talked to Greg a bit and we discussed joining multiple lobby types at once. For now, I plan to search for multiple lobbies at once and cancel matchmaking for any possible 2nd joined lobbies.

Thanks @Paul-Winterhalder

WOW, Thank you 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.

@Paul-Winterhalder Thanks Paul, looking forward to any possible solutions.

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.