Sonos test suite fails on counting items in new playlist - sonos

I have a container (music show) with 19 tracks in it and 1 item for recommendations section for this show. So totaly there are 20 items. But if I am adding this show to playlist, only tracks will be processed and playlsit will contain 19 tracks. Sonos controller is working fine with it, but Test Suite fails with checking total items after adding show to playlist with message
FAIL The seed playlist and newly created playlist should have the same
quantity of items inside. (expected 19 != actual 20)
As the result Test Suite fails with 1 error. Is it O.K. to send test suite report with such fail? Or you will deny new service with such fail?
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns1="http://www.sonos.com/Services/1.1">
<SOAP-ENV:Body>
<ns1:getMetadataResponse>
<ns1:getMetadataResult>
<ns1:index>0</ns1:index>
<ns1:count>20</ns1:count>
<ns1:total>20</ns1:total>
<ns1:mediaCollection>
<ns1:id>CONTAINER:RECOMMENDATIONS:594</ns1:id>
<ns1:itemType>collection</ns1:itemType>
<ns1:displayType>grid</ns1:displayType>
<ns1:title>Recommendations</ns1:title>
<ns1:canPlay>false</ns1:canPlay>
<ns1:canAddToFavorites>false</ns1:canAddToFavorites>
</ns1:mediaCollection>
<ns1:mediaMetadata>
<ns1:id>TRACK:11422:594</ns1:id>
<ns1:itemType>track</ns1:itemType>
<ns1:displayType>list</ns1:displayType>
<ns1:title>He Ain't Give You None</ns1:title>
<ns1:summary>The Radiators</ns1:summary>
<ns1:mimeType>audio/mp3</ns1:mimeType>
<ns1:trackMetadata>
<ns1:artist>The Radiators</ns1:artist>
<ns1:duration>531</ns1:duration>
<ns1:rating>0</ns1:rating>
<ns1:canPlay>true</ns1:canPlay>
<ns1:canSkip>true</ns1:canSkip>
</ns1:trackMetadata>
</ns1:mediaMetadata>
<ns1:mediaMetadata>
<ns1:id>TRACK:58012:594</ns1:id>
<ns1:itemType>track</ns1:itemType>
<ns1:displayType>list</ns1:displayType>
<ns1:title>Alimony</ns1:title>
<ns1:summary>The Radiators</ns1:summary>
<ns1:mimeType>audio/mp3</ns1:mimeType>
<ns1:trackMetadata>
<ns1:artist>The Radiators</ns1:artist>
<ns1:duration>632</ns1:duration>
<ns1:rating>0</ns1:rating>
<ns1:canPlay>true</ns1:canPlay>
<ns1:canSkip>true</ns1:canSkip>
</ns1:trackMetadata>
</ns1:mediaMetadata>
[MORE ITEMS HERE]
</ns1:getMetadataResult>
</ns1:getMetadataResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

I am taking some liberties in answering your question since it seems to be directed at Sonos, so apologies in advance. It is very unlikely that your service will be rejected for a bug that happens to be inside Sonos test suite.
So my two cents, go for it and submit your service.

I believe that the issue here is that a playlist is defined as container specifically full of track elements (http://musicpartners.sonos.com/node/286) and your playlist contains a collection. This is why this is failing to generate the correct count in the test.

Related

SONOS getMediaURI endpoint not called by player

I’m developing a custom music service for SONOS in which custom playlists are provided to be played (Spotify alike).
I’ve implemented the required endpoints and I can see while debugging that the GETLASTUPDATE and GETMETADATA endpoints are called and that the information is show in the APP (Playlists list, track list by playlist and artist and album info).
The issue is, When I try to reproduce a complete playlist or a track I get an
Unable to add songs to Queue
message and no call is done by the app to the API.
What am I missing here?
Below you may find the called the endpoints output.
Request:
<getMetadata xmlns="http://www.sonos.com/Services/1.1">
<id>root</id>
<index>0</index>
<count>100</count>
</getMetadata>
Response:
<ns1:getMetadataResponse>
<ns1:getMetadataResult>
<ns1:index>0</ns1:index>
<ns1:count>9</ns1:count>
<ns1:total>9</ns1:total>
<ns1:mediaCollection>
<ns1:id>PLAYLIST:10:2</ns1:id>
<ns1:itemType>playlist</ns1:itemType>
<ns1:title>Anos 90</ns1:title>
<ns1:summary>Relembre os hits que marcaram os anos 90. Da música pop ao grunge, esta playlist conta com as presenças de Alanis Morissette, Oasis, Pearl Jam e The Cranberries</ns1:summary>
<ns1:canPlay>true</ns1:canPlay>
<ns1:albumArtURI>https://xxx/xxdata/images/playlists/default.jpg</ns1:albumArtURI>
</ns1:mediaCollection>
</ns1:getMetadataResult>
</ns1:getMetadataResponse>
Request:
<getMetadata xmlns="http://www.sonos.com/Services/1.1">
<id>PLAYLIST:10:2</id>
<index>0</index>
<count>100</count>
</getMetadata>
Response:
<ns1:getMetadataResponse>
<ns1:getMetadataResult>
<ns1:index>0</ns1:index>
<ns1:count>100</ns1:count>
<ns1:total>338</ns1:total>
<ns1:mediaMetadata>
<ns1:id>track:300</ns1:id>
<ns1:title>Black Hole Sun</ns1:title>
<ns1:mimeType>audio/mp3</ns1:mimeType>
<ns1:itemType>track</ns1:itemType>
<ns1:trackMetadata>
<ns1:albumId>album:1390</ns1:albumId>
<ns1:duration>253970</ns1:duration>
<ns1:artistId>artist:543</ns1:artistId>
<ns1:artist>Soundgarden</ns1:artist>
<ns1:album>Superunknown</ns1:album>
<ns1:albumArtURI>https://xxxx/musiccover.aspx?pk=xxx-xxx-xxxx-xxxx</ns1:albumArtURI>
</ns1:trackMetadata>
</ns1:mediaMetadata>
<ns1:mediaMetadata>
<ns1:id>track:514</ns1:id>
<ns1:title>Don't Speak</ns1:title>
<ns1:mimeType>audio/mp3</ns1:mimeType>
<ns1:itemType>track</ns1:itemType>
<ns1:trackMetadata>
<ns1:albumId>album:1128</ns1:albumId>
<ns1:duration>207196</ns1:duration>
<ns1:artistId>artist:467</ns1:artistId>
<ns1:artist>No Doubt</ns1:artist>
<ns1:album>Tragic Kingdom</ns1:album>
<ns1:albumArtURI>https://xxxx/musiccover.aspx?pk=xxx-xxx-xxxx-xxxx</ns1:albumArtURI>
</ns1:trackMetadata>
</ns1:mediaMetadata>
</ns1:getMetadataResult>
</ns1:getMetadataResponse>
Is that last snippet your actual response? It could be a number of things, but I think the issue may be that your response claims to return 100 results when it only contains 2. To test this, try to use
<ns1:index>0</ns1:index>
<ns1:count>2</ns1:count>
<ns1:total>2</ns1:total>
<ns1:mediaMetadata>. . . <ns1:mediaMetadata>
<ns1:mediaMetadata>. . . <ns1:mediaMetadata>
instead of count=100, total=338. The player may be trying to enqueue the rest of the tracks and failing to do so, causing the error.
If you use the ... menu on the track from the Sonos app's browse, and select "Play Song" the player should enqueue only the one track and attempt to play it without dealing with the pagination of the playlist container.

Prestahop api 1.7 update order webservice error

I'm triyng to update an order status & tranking number on prestashop 1.7.6.0 via webservice but if the new order status has to send email to customer I get error 500.
Cases:
new order status id 5 send email > error 500 (status changed, no mail sent, other changes like track nr ignored)
new order status id 4 doesn't send email > code 200 (all ok)
BUT if I try changing manually in back office to order status id 5 all is working, status changed and mail sent.
I do all my test on Postman as these information will be changed with a call from an external service for the management of shipment, how can I debug this problem?
End Point: www.domain.ext/api/orders/10705
xml sent
<?xml version="1.0" encoding="UTF-8"?>
<prestashop xmlns:xlink="http://www.w3.org/1999/xlink">
<order>
<id>10705</id>
<id_address_delivery xlink:href="https://www.domain.ext/api/addresses/11307">11307</id_address_delivery>
<id_address_invoice xlink:href="https://www.domain.ext/api/addresses/11307">11307</id_address_invoice>
<id_cart xlink:href="https://www.domain.ext/api/carts/11918">11918</id_cart>
<id_currency xlink:href="https://www.domain.ext/api/currencies/2">2</id_currency>
<id_lang xlink:href="https://www.domain.ext/api/languages/2">2</id_lang>
<id_customer xlink:href="https://www.domain.ext/api/customers/10806">10806</id_customer>
<id_carrier xlink:href="https://www.domain.ext/api/carriers/5">5</id_carrier>
<current_state xlink:href="https://www.domain.ext/api/order_states/5">5</current_state>
<module>codwfeeplus</module>
<invoice_number>0</invoice_number>
<invoice_date>2022-05-10 15:32:41</invoice_date>
<delivery_number>9050</delivery_number>
<delivery_date>2022-05-17 15:16:33</delivery_date>
<valid>1</valid>
<date_add>2022-05-10 15:32:40</date_add>
<date_upd>2022-05-17 15:23:53</date_upd>
<shipping_number notFilterable="true">1592222222</shipping_number>
<id_shop_group>1</id_shop_group>
<id_shop>1</id_shop>
<secure_key>044248612d0019be079f165138d46e85</secure_key>
<payment>CONTRASSEGNO</payment>
<recyclable>0</recyclable>
<gift>0</gift>
<gift_message/>
<mobile_theme>0</mobile_theme>
<total_discounts>0.000000</total_discounts>
<total_discounts_tax_incl>0.000000</total_discounts_tax_incl>
<total_discounts_tax_excl>0.000000</total_discounts_tax_excl>
<total_paid>15.500000</total_paid>
<total_paid_tax_incl>15.500000</total_paid_tax_incl>
<total_paid_tax_excl>15.500000</total_paid_tax_excl>
<total_paid_real>15.500000</total_paid_real>
<total_products>9.500000</total_products>
<total_products_wt>9.500000</total_products_wt>
<total_shipping>6.000000</total_shipping>
<total_shipping_tax_incl>6.000000</total_shipping_tax_incl>
<total_shipping_tax_excl>6.000000</total_shipping_tax_excl>
<carrier_tax_rate>0.000</carrier_tax_rate>
<total_wrapping>0.000000</total_wrapping>
<total_wrapping_tax_incl>0.000000</total_wrapping_tax_incl>
<total_wrapping_tax_excl>0.000000</total_wrapping_tax_excl>
<round_mode>2</round_mode>
<round_type>1</round_type>
<conversion_rate>1.000000</conversion_rate>
<reference>10705</reference>
<associations>
<order_rows nodeType="order_row" virtualEntity="true">
<order_row>
<id>10913</id>
<product_id xlink:href="https://www.domain.ext/api/products/203975">203975</product_id>
<product_attribute_id>0</product_attribute_id>
<product_quantity>1</product_quantity>
<product_name>xxxxxxxxxxxxxxxxxxxx</product_name>
<product_reference>12859</product_reference>
<product_ean13/>
<product_isbn/>
<product_upc/>
<product_price>10.000000</product_price>
<id_customization xlink:href="https://www.domain.ext/api/customizations/0">0</id_customization>
<unit_price_tax_incl>9.500000</unit_price_tax_incl>
<unit_price_tax_excl>9.500000</unit_price_tax_excl>
</order_row>
</order_rows>
</associations>
</order>
</prestashop>
I found it's a Prestashop 1.7.6 WS bug
https://github.com/PrestaShop/PrestaShop/issues/14842
Solved here https://github.com/PrestaShop/PrestaShop/pull/14899

Bit rate error when trying to dial out to an ISDN line using Polycom XML API

I am having a problem connecting to an ISDN line using Polycom's XML API on an RMX_2000. Below is the request I am sending, and the response. I can do the same action from the RMX Manager, for the same number, in the same conference, and it works. When I trace the XML from the RMX Manager, I get an ADD_PARTY request that looks exactly like my constructed request, except with a lot more elements. I've reviewed and don't see any that seem like they could be relevant, and I am loath to manually code every single element, knowing that it is a long shot that it will even help. The same request (variant) works fine for IP and registered number requests, but no matter what I do, always get the bit rate error below. Can anyone tell me what I am doing wrong?
<TRANS_CONF_1>
<TRANS_COMMON_PARAMS>
<MCU_TOKEN>304</MCU_TOKEN>
<MCU_USER_TOKEN>304</MCU_USER_TOKEN>
<MESSAGE_ID>1</MESSAGE_ID>
</TRANS_COMMON_PARAMS>
<ACTION>
<ADD_PARTY>
<ID>18466</ID>
<PARTY>
<ID>0</ID>
<NAME>isdn</NAME>
<PHONE_LIST>
<PHONE1>12345678910</PHONE1>
</PHONE_LIST>
<INTERFACE>isdn</INTERFACE>
<CONNECTION>dial_out</CONNECTION>
<MEET_ME_METHOD>party</MEET_ME_METHOD>
<NUM_TYPE>taken_from_service</NUM_TYPE>
<MULTI_RATE>auto</MULTI_RATE>
<ALIAS>
<NAME>12345678910</NAME>
<ALIAS_TYPE>323_id</ALIAS_TYPE>
</ALIAS>
<VIDEO_BIT_RATE>automatic</VIDEO_BIT_RATE>
<ENHANCED_VIDEO>false</ENHANCED_VIDEO>
<UNDEFINED>false</UNDEFINED>
</PARTY>
</ADD_PARTY>
</ACTION>
</TRANS_CONF_1>
Here is the response:
<RESPONSE_TRANS_CONF>
<RETURN_STATUS>
<ID>1015</ID>
<DESCRIPTION>Conference bit rate must be set to a minimum of 128Kbps to enable ISDN participant connection</DESCRIPTION>
<YOUR_TOKEN1>0</YOUR_TOKEN1>
<YOUR_TOKEN2>0</YOUR_TOKEN2>
<MESSAGE_ID>1</MESSAGE_ID>
<DESCRIPTION_EX></DESCRIPTION_EX>
</RETURN_STATUS>
<ACTION>
<ADD_PARTY/>
</ACTION>
</RESPONSE_TRANS_CONF>
Thanks to a little help from someone at Polycom, I found out that the following node is required for this:
auto
I added that to the PARTY node, and now all is well.
After alot of troubleshooting and wiresharking on this error I found a combination of 2 properties being the issue
Reservation object needs
<TRANSFER_RATE>384</TRANSFER_RATE>
Party object needs
<NET_CHANNEL_NUMBER>auto</NET_CHANNEL_NUMBER>

highrise API, put unprocessable entity , 37 Signals

i´m playing arround with the HIGHRISE API, and they understood the meaning of rest, its pretty cool and at some points gracefully forgivingly, but
has anybody any idea why the xml i PUT is not accepted ?
here is some relevant logging :
2014-02-23 00:00:04] app.INFO: Updating:Person:Highrise-API = people/11834527375.xml [] []
[2014-02-23 00:00:04] app.INFO: request body is :
<?xml version="1.0" encoding="UTF-8"?>
<person>
<first-name><![CDATA[Johnny]]></first-name>
<last-name><![CDATA[B. Good]]></last-name>
<visible-to><![CDATA[Everyone]]></visible-to>
<subject_datas type="array">
<subject_data>
<subject_field_id type="integer"><![CDATA[43212]]></subject_field_id>
<value><![CDATA[dsa328394OOKD323H]]></value>
</subject_data>
<subject_data>
<subject_field_id type="integer"><![CDATA[470259]]></subject_field_id>
<value><![CDATA[provider://w184071823/fmdks/2032]]></value>
</subject_data>
<subject_data>
<subject_field_id type="integer"><![CDATA[469130]]></subject_field_id>
<value><![CDATA[CORE]]></value>
</subject_data>
<subject_data>
<subject_field_id type="integer"><![CDATA[469132]]></subject_field_id>
<value><![CDATA[Way too cool]]></value>
</subject_data>
</subject_datas>
<contact-data>
<phone-numbers>
<phone-number type="array">
<number><![CDATA[081 6418273]]></number>
<location><![CDATA[Work]]></location>
</phone-number>
</phone-numbers>
<addresses type="array">
<address>
<city><![CDATA[New York City]]></city>
<country><![CDATA[US]]></country>
<state><![CDATA[New York]]></state>
<street><![CDATA[Siplingerstreet 11]]></street>
<zip><![CDATA[87527]]></zip>
<location><![CDATA[Work]]></location>
</address>
</addresses>
</contact-data>
</person>
[] []
[2014-02-23 00:00:04] app.INFO: request set [] []
[2014-02-23 00:00:04] app.ERROR: Guzzle/3.8.1 curl/7.28.1 PHP/5.4.10 - [2014-02-22T23:00:04+00:00] "PUT /people/11834527375.xml HTTP/1.1" 422 103 [] []
[2014-02-23 00:00:04] app.INFO: Caught client-error-exception in HighriseService updatePerson(): exception 'Guzzle\Http\Exception\ClientErrorResponseException' with message 'Client error response
[status code] 422
[reason phrase] Unprocessable Entity
i dont see the error :/
I´m very sure the subject_field_id´s are correct and those custom fields are set
Posting e.g saving that xml works, i saw from the response that are fields were set,
only thing i can guess is, that i´m trying to PUT a version where nothing has changed,
is that the problem ?
because my code only checks if that person exists at all and if so update it instead of creating
You should get back some XML in the body of the response. It should look like this:
<?xml version="1.0" encoding="UTF-8"?>
<errors>
<error>Phone number '555-555-5555' has already been taken</error>
</errors>
If you include the id for the existing phone number in your PUT request, then we know that you want to update the existing address, rather than adding a new one: https://github.com/basecamp/highrise-api/blob/master/sections/people.md#update-person
Contact data and Subject data that include an id will be updated, data that doesn’t will be assumed to be new and created from scratch. To remove a piece of data, prefix its id with a minus sign (e.g. -1).

ebay API GetOrders shows wrong result

My objective is to list user's transactions (both sales and purchases).
I am using GetOrders and specifying a time range to and the call executes successfully but returns 0 transactions, whereas the user I am querying for has multiple purchases on their account.
Let me get a bit more specific. Here is the code that I am using:
<GetOrdersRequest xmlns="urn:ebay:apis:eBLBaseComponents">
<RequesterCredentials>
<eBayAuthToken>......</eBayAuthToken>
</RequesterCredentials>
<CreateTimeFrom>2009-04-05T05:02:03</CreateTimeFrom>
<CreateTimeTo>2011-12-23T00:02:44</CreateTimeTo>
</GetOrdersRequest>​
And even using the API test tool (Hence, the problem is not language specific) it delivers 0 results:
<GetOrdersResponse xmlns="urn:ebay:apis:eBLBaseComponents">
<Timestamp>2011-12-23T00:05:32.753Z</Timestamp>
<Ack>Success</Ack>
<Version>753</Version>
<Build>E753_CORE_BUNDLED_14214525_R1</Build>
<PaginationResult>
<TotalNumberOfPages>0</TotalNumberOfPages>
<TotalNumberOfEntries>0</TotalNumberOfEntries>
</PaginationResult>
<HasMoreOrders>false</HasMoreOrders>
<OrderArray />
<OrdersPerPage>100</OrdersPerPage>
<PageNumber>1</PageNumber>
<ReturnedOrderCountActual>0</ReturnedOrderCountActual>
</GetOrdersResponse>​`
The user I am querying for has 2 recent purchases dated at:
12/08/11
11/18/11
What am I missing here? I am supplying the time range and the call executes properly, yet it finds 0 results. I'd very much appreciate your help.
Try including the OrderRole, ie. Buyer or Seller and OrderStatus of either Active or Completed. Something like the following will return completed orders for items purchased by the caller.
<GetOrdersRequest xmlns="urn:ebay:apis:eBLBaseComponents">
<DetailLevel>ReturnAll</DetailLevel>
<MessageID>cff8bc1c-0475-4d64-a8a5-02757aafd937</MessageID>
<Version>747</Version>
<CreateTimeFrom>2012-01-07T14:05:24.6353866Z</CreateTimeFrom>
<CreateTimeTo>2012-02-07T14:05:24.6353866Z</CreateTimeTo>
<OrderRole>Buyer</OrderRole>
<OrderStatus>Completed</OrderStatus>
</GetOrdersRequest>
For more details, have a look here.
The maximum date range that may be specified is 30 days