View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010508 | MMA | UPnP / Casting | public | 2013-02-11 18:27 | 2013-02-12 12:41 |
| Reporter | marek | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0010508: Incorrect format of integers in UPnP messages | ||||
| Description | There are some issues with parsing of integers that are sent to MMA from MMW during wifi sync. I have only 1 example so far, but this issue is very common: <upnp:originalTrackNumber>5/9</upnp:originalTrackNumber> Is it possible to check the correct format of integers on MMW side? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 100 | ||||
|
|
@Marek For testing what format is expected to be received in MMA? What do you suggest that MMW always serve Integer value only even value is String? |
|
|
I have revised the code and tested and haven't found a problem. MMW always sends <upnp:originalTrackNumber> as integer value. i.e. if you edit track# in MMW to '5/9' then MMW serves <upnp:originalTrackNumber>5</upnp:originalTrackNumber> Are you sure that it was MMW server that served the fractional 5/9 value? |
|
|
No, it can be another type of server. I will resolve this and open new issue. |
|
|
Verified in 100 |
