Since v4 of the plugin, by default the built-in UI behaviour will ask users if they want to remember their selected app to use next time, rather than asking them each time. However, if they choose to remember their choice, and subsequently uninstall their preferred app (bit of an edge case, but possible), then the plugin currently continues to attempt to launch the uninstalled app, without first checking if it's still installed.
The result is, not only does the navigator app obviously not launch, but (on Android at least) neither the success or error callback is invoked. It looks like the native Android layer is catching the exception, but not passing it on to the error callback:
LaunchNavigator[native]: Exception occurred: No Activity found to handle Intent { act=android.intent.action.VIEW dat=lyft://ridetype?id=lyft&destination[latitude]=53.4807593&destination[longitude]=-2.2426305&pickup[latitude]=51.5073509&pickup[longitude]=-0.1277583 }
Since v4 of the plugin, by default the built-in UI behaviour will ask users if they want to remember their selected app to use next time, rather than asking them each time. However, if they choose to remember their choice, and subsequently uninstall their preferred app (bit of an edge case, but possible), then the plugin currently continues to attempt to launch the uninstalled app, without first checking if it's still installed.
The result is, not only does the navigator app obviously not launch, but (on Android at least) neither the success or error callback is invoked. It looks like the native Android layer is catching the exception, but not passing it on to the error callback: