Ciao @Greg-Moulds,
you rock boy! 🙂
I tried reducing the "early" launch setting as you suggested and in fact now the waiting time is very short. That was exactly the problem.

Thanks!

I just got our iOS Push Notifications working with brainCloud and would like to add a few tips to this thread.

For the less Mac-Savvy developers like me, here's what it looks like when you only have your certificate with no private key to export as a P12 file:

Screen Shot 2019-06-19 at 4.02.20 PM.png

Notice the selected category is [My Certificates]. Certificates in the [Certificates] category have the P12 export option greyed out.

I am using Unity as a development platform and for some reason my device would only receive Development Push Notifications even when running in Release in Xcode. It's only after uploading to TestFlight that my Production Push Notifications started working.

It's really useful post,[url=https://www.latestdatabase.com/]Buy Email Database[/url]
thanks for sharing your information See more details....

@David-St-Louis-0 @Paul-Winterhalder
Hi again.
I would like to debug my server locally, in Unity. I have the _S2S stuff all hooked up as described in the walk through.
But then I tried to do the following (actual numbers redacted)

#if UNITY_EDITOR var appId = "00000"; var serverName = "MyServerName"; var secret = "00000000-0000-0000-0000-000000000000"; _lobbyId = "00000:myLobbyTypeId:00"; #else // Load environment variables passed in by brainCloud to our container var appId = Environment.GetEnvironmentVariable("APP_ID"); var serverName = Environment.GetEnvironmentVariable("SERVER_NAME"); var secret = Environment.GetEnvironmentVariable("SERVER_SECRET"); _lobbyId = Environment.GetEnvironmentVariable("LOBBY_ID"); #endif

However, I am getting a perpetual error:
#S2S S2S Failed: {"packetId":1,"messageResponses":[{"reason_code":40613,"status_message":"Processing exception: Unrecognized lobby: 00000:myLobbyTypeId:00","status":400}]}

I even signed up for a Dev+ subscription, just in case that was the problem, per this thread. No luck.

How can I test my server code locally, while still planning for the full-on S2S Docker container deployment?
Thanks

Yup. We as devs often resist change. Hopefully you'll come to appreciate Portal-X as you use it more!

Hi Alessio,

I have a suggestion.

Why not create a global chat channel called "lobbyListeners".

Then - when a user is viewing the lobbies - have them connect to and listen to the lobbyListeners channel.

Then you don't need to maintain a global entity at all. Whenever you create a lobby or delete it - send an event to lobbyListeners - and it will automatically send it to everyone who has registered for the channel.

Would that work? (or is there a part of your use case that I am missing?)

Paul.

@JasonL
Thank you for the info, much appreciated!

Cool. Thanks for sharing the solution here @devsleeper !

Hi @Panagiotis-Milios ,

Yup - we made improvements to the Entity Viewer(s) partially based on your feedback. There are more improvements to come as well.

We're also looking at the Job Queue screen - and I've passed the Ctrl-S request onto the Cloud Code Editor dev... I definitely agree with that - it's a reflex for lots of folks (including me!).

Paul.

Sounds good Ali - thanks for the confirmation!

Paul.

@Brad-Hester That bug has been fixes (and patched). Thanks for reporting it!

Hi,
Any updates on what's coming up on the Builder API?
I've been using it so far to automate the deployment of cloudscripts during development and has been a great time saver so far. I'd like to know or if you have some kind of a timeframe of when we can expect "Global Properties" to be available. Cause having would allows us to automate deployment of configuration files too.

Also, is the Builder API going to able to make calls to interact with entities? We're migrating from gamesparks, and a useful tool for liveops was to build custom screens that would serve as tools for interacting with user data. Since Braincloud doesn't have that feature, we're looking into rebuilding those screens in Unity, but the missing piece of the puzzle is that we need a way to have access to entity data.

Thank you for your time!
J.B.

We'll look into it @Omar-Alzayed ...

Paul.

Hi folks,

FYI, here's one minor update regarding the Retention Analytics screen:

We have changed it to show Classic retention by default.

The reason for the change is that Rolling Retention naturally trends downward over the 30-day period of the report. That's simply due to mathematics. Rolling retention for a particular day measures whether the user returns that day - or any day thereafter. Thus - the days at the end of the calendar period have fewer days after them - and so the stat will naturally be lower.

We don't want folks to mistakenly think their retention is trending down - so we're now defaulting to Classic Retention which is more deterministic over the 30 day period. For those who wish to view the Rolling Retention - it's just a mouse click away!

Cheers!

Paul.

thx, I will give it a try

For clarity, Firebase Cloud Messaging recommends creating a topic using Pub/Sub, though this approach is optional.

Ciao @Paul-Winterhalder ,

yes there is not much else to add, except perhaps the fact that the CompleteMatch is sent at the end of the game. Instead, AbandonMatch is sent if one of the players abandons the game prematurely.

Thanks for the support! 🙂

@Travis-Brown-John You can create them manually from the Monitoring menu.

Monitoring | Global Monitoring | Global Entities.

Note - if your app is live, you need to unlock it first. You'll see a bit [+] button to the right of the Bulk actions drop-down.

Good luck!

Paul.

No problem! glad to hear that.

@Paul-Winterhalder said in A few suggestions I have so far:

. Would it be fair to say that those user's entities would have to have their ACL set to other: 1 so it's readable?

Yes, that would be the case.