We've deployed the patch for this. Apologies for the delay!
brainCloudAdmin
brainCloud personnel
Posts
-
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1 -
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1Okay - it looks like that script may be callable via cloud code script in S2S - but not via the S2S api directly... The devs are looking into it.
-
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1Hi guys,
Can you still get this error? We can't repro it?
Paul.
-
Integration streamCase 14697
-
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1Added case 14696
Linked to cases 14550 and 14677 -
Integration streamHi Noah, thanks for the follow-up. Yes, for virtual item purchases, the stream event is triggered immediately in the same request flow, right after the purchase is finalized and verified. So the trigger point is immediate.
That said, the event delivery to downstream systems such as Kafka, Segment, or the Mongo log is asynchronous and queued, so it should not be treated as a synchronous low-latency real-time event.
We’ll also review your feature request for a Stream HTTP Webhook and will keep you posted.
-
[Feature request] Support multiple Apple client IDs (aud values) for AuthenticateAppleAwesome. Thanks for confirming @lee-jong-gun !
-
Request to add unique indexes for Custom EntitiesActually that should work now @moondory77 . You just have to include "unique": true in the options.
-
Subject: Inquiry regarding selective CustomEntity migration via Builder APICool - glad you found it!
-
Confirming Campaign feature write API limitations and Trigger timing (v6.0)Hi @jongdae.won ,
brainCloud 6.0.1 has been deployed. The Campaign Analytics feature - as well as the APIs for updating the campaign and scenario JSON, are now live!
Paul.