Bug in the API?

Support
#1

Is there a bug in the search part of the API? I’m developing a companion app that listens for the mood playing by performing a search (/search/?playing=Playing%20Now&format=json). Works a treat on what I thought was all moods. But in testing the Sticky Situation oneshot I noticed my app wasn’t showing the playing mood. The API search call also show no playing sounds at all, which isn’t true because I can hear them.

In the screenshots I have the Goblin Arrows Aftermath mood playing and I get an expected result in the API. If I then switch to the Sticky Situation Ailwen Manor mood, the API search returns 0 for what’s playing. I’ve checked direct on https://syrinscape.com/search/?playing=Playing%20Now&format=json and I get the same 0 playing result.

A bug? Could you guys take a look please?

syrinscape-soundboard_playing
syrinscape-soundboard_playing3238×1172 379 KB
syrinscape_soundboard_api_search_good
syrinscape_soundboard_api_search_good878×680 47.4 KB
syrinscape_soundboard_no_product_or_pack_playing
syrinscape_soundboard_no_product_or_pack_playing3260×1190 379 KB
syrinscape_soundboard_api_search_nothing_playing
syrinscape_soundboard_api_search_nothing_playing858×696 41.6 KB

1 Like
#2

Thanks for the report! As best I can tell, this is not a logic bug, but a symptom of a more general known issue we have with keeping the search index up to date as new content is created and modified. The SoundSet for the A Sticky Situation adventure was missing from the index, so could not be returned in any search query, not just those limited to “Now Playing”. We have no ETA as yet as to when we will get to resolving this stale index issue, but we did manually bump this SoundSet so that particular content at least should be working now.

You may also want to consider implementing the Javascript Player API: https://docs.syrinscape.com/javascript-player/. This may be heavy handed if you don’t want your interface to be making sounds, but it does come with Javascript Events that may do a better job of monitoring Mood changes for you, rather than making calls to the /search/ endpoint, which can suffer from stale content problems, and if nothing else requires a HTTP request/response round trip to our server, when the JS events listen to WebSocket messages so can be somewhat more responsive.

Hope this helps!

1 Like
#3

Thanks. I’ll take a look at the player for the events. In all the dev and testing that’s the only issue I ever, saw from the API, so it’s pretty stable everywhere else.

1 Like