Condition issue with Android/Messenger client

[andreasdieryck]

@BillyWaveM has created two sequences:

1. the first sequence (https://github.com/GhostWording/gw-config-apis/blob/master/data/bot/sequences/appspecials/fortnite/FortniteHeard.json) sets a condition ppPlayFortnite (line 91)
2. the second sequence opens on the "Condition": "ppPlayFortnite == 'true'"

We've put those two sequences in several bots (nuttynow, surveyios, surveyapps, louisjshotbot). Here's what happened when we tried these botnames in the three different clients:

A. On Android

After "Tu y joues", here's what's supposed to happen:

• in the background, ppPlayFortnite is set to true
• then sequence 2 should pop up, since "Condition": "ppPlayFortnite == 'true'"

However, after answering "Yes" to "Tu y joues", I don't see sequence 2 on Android ❌

B. On Messenger

Again, after "Do you play it?", here's what's supposed to happen:

• in the background, ppPlayFortnite is set to true
• then sequence 2 should pop up, since "Condition": "ppPlayFortnite == 'true'"

However, after answering "Yes" to "Do you play it", I don't see sequence 2 on Messenger❌

C. On iOS

Again, after "Tu y joues?", here's what's supposed to happen:

• in the background, ppPlayFortnite is set to true
• then sequence 2 should pop up, since "Condition": "ppPlayFortnite == 'true'"

This time, sequence 2 is triggered: the condition is working properly with the iOS client ✅

We have made several test to confirm this issue and they all come to the same conclusion: sequence 2 is only triggered on the iOS client, neither on Android nor on Messenger

What do you think about it @rhwy ? How can we help you find the issue?

[rhwy]

for that kind of stuff you absolutely need to do the tests with postman to see what happen in order to first see if the problem is on the server side or the client side.

manually the steps would be:

• get first sequence (as an app should do)
• if there's a SetUserProperty in the sequence, manually send the ppPlayFortnite=true property to the user's property service
• ask for second sequence to see if the precondition is working (conditions are now evaluated on server side and not on client side)

everything for making these calls is documented here https://github.com/GhostWording/PublicDocumentation/blob/master/API/Sections/SequencesBotApis.md

For me this sounds like android not sending correctly the property. we also have to be sure that the calls are done for all apis with the exact same identifiers {deviceid, facebookid, botname}.

I also had this kind of situation on messenger bots but only when I try to evaluate a condition just after set the property but it was because I was in the same request and the context with the new property didn't refreshed yet from the database. But it's something that can't happend on apis side ;)

[rhwy]

@andreasdieryck could you re-test this after my comment just to confirm we can close the issue ?