[TIMOB-1941] Android: erroneous state (playing) when invalid url is entered in remote streaming test case
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:57:36.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.6.0 M05 |
| Components | Android |
| Labels | android, defect, release-1.6.0, sound, streaming |
| Reporter | Thomas Huelbert |
| Assignee | Don Thorp |
| Created | 2011-04-15T03:06:10.000+0000 |
| Updated | 2011-04-17T01:57:36.000+0000 |
Description
1.4.2.5935b3 G1 running 1.6
1.Phone>sound>Remote streaming
2.enter some chars into the field, tap "start stream"
results:State reports itself as playing
the script is
streamer.addEventListener('change',function(e)
{
stateLabel.text = 'State: '+e.description +' ('+e.state+')';
});
(from [1ed9dd73c98ce535b6b1f2101502009a6d061372]) [#1941 state:fixed-in-qa] changes TiSound to return stopped state when play fails
TiSound.play will not return a stopped state when a play call fails inside the initialize method. Updated KS example to handle the stopped state correctly and update the screen with the proper play state and status
https://github.com/appcelerator/titanium_mobile/commit/1ed9dd73c98ce535b6b1f2101502009a6d061372"> https://github.com/appcelerator/titanium_mobile/commit/1ed9dd73c98c...
The fix can be verified via the updated KS test case (part of the commit for this ticket) mentioned in the first post.
Verified on G1/1.6 and Nexus One/2.2.1 using build #e1cb22a