[TIMOB-2072] Android: Network change event fired unexpectedly on first launch
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2011-06-02T13:39:13.000+0000 |
| Affected Version/s | Release 1.5.0 |
| Fix Version/s | Sprint 2011-22 |
| Components | Android |
| Labels | android, android_refactor, defect, regression, tbf-1.7.0 |
| Reporter | Thomas Huelbert |
| Assignee | Opie Cyrus |
| Created | 2011-04-15T03:09:41.000+0000 |
| Updated | 2011-06-02T13:39:13.000+0000 |
Description
1.Platform>Network
results: change event reports itself as having been fired.
2.back buton, retry test case
results: change event not fired.
notes test again an no such result. uninstall/reinstall (or force quit) relaunch and see it again.
Network listener is attached the first time the event listener for the 'change' is added or when the application (root activity) is resumed. In the KitchenSink example, the first time the test is opened the registration for the 'change' event causes the network listener to be initially attached and the first event to be fired. If you back out of the test and then open it then you will not see a new 'change' event because the network listener is still attached and the network state has not changed. If you were to hit 'home' when inside the network test, turn on airplane mode and then come back into KitchenSink you would see that the network state has changed due to a new 'change' event that fired when the airplane mode was enabled or disabled. Verified behavior on Droid 2(2.2)
Working as expected, not a bug