It's complicated. This discrepancy was discovered and reported in https://jira.appcelerator.org/browse/TC-1846 in February. According to the issue responder, we should not be using this callback at all in MobileWeb/Tizen, because it's not supported in MobileWeb *). However, in fact it is supported, but the signature of the response is different than in other OSes. And we got Geocoder working, albeit with a workaround. Which may not have been the best thing to do.

So please advise if 

* the test should be deactivated in MW/Tizen (as it's using an undocumented feature), or 
* the change should be reverted and the test allowed to fail.

_______________________
*) Which renders the entire Ti.Geolocation.forwardGeocoder() and friends as not implemented, because the callback is the only useful result. Therefore this function cannot be advertised as supported in MW?