[TIMOB-2418] Android: Geolocation - updated heading heading not fired (g2, droid 1), updated location returning error:{} droid 1.
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2017-06-07T22:32:15.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Android |
| Labels | android, defect, geolocation |
| Reporter | Thomas Huelbert |
| Assignee | Ingo Muschenetz |
| Created | 2011-04-15T03:19:12.000+0000 |
| Updated | 2017-06-07T22:32:15.000+0000 |
Description
Titanium SDK version: 1.7.0 (Apr 12 2011 15:24 rcc9dd9e1) Nexus
S and Droid 1
1.5.0.91838a G2 (2.2) droid1 (2.2)
1.Phone > Geolocation
2.note values, check console
results:
G2 - updated heading heading not fired.
droid 1 - updated heading heading not fired, updated location
returning error:{}
Nexus S - Updated Location not fired, Reverse Geo (Cooords ->
ADDR) is NULL
Expected:
To get values for all
as of mondays pull [INFO] Titanium SDK version: 1.5.0 (11/29/10 08:10 faa27c7), the behavior has changed. Now:
G2:
updated heading not firing
current and updated location returning null
Reverse geo not populating
nexus one invokes alert on test case load
error {code. G2 works as expected.
Titanium SDK version: 1.5.0 (12/10/10 09:14 0c31e15)
Reverse geo not populating with Nexus S. Also can't seem to get section of code that includes the reverse geo block to run. No added traces appear in the log. This may be why there is no alert presented for the failure of the reverse geo. In addition, according to Chung, the calls may be malformed. Where the call should have "aguid=", they only have "aguid".
Closing ticket due to time passed and lack of work.