Description
My Xamarin Forms application interacts with some hardware and needs permission to use Bluetooth and/or USB to function at all, so we end up triggering a permissions dialog at startup. It caused me to bump into this issue, but I think this is an inelegant solution.
If there are things that can go wrong if the application does them before Calabash finishes loading, I feel like loading Calabash should either block until it finishes or provide some mechanism to notify me it is finished. For example, I wouldn't mind inserting a loading page to my application and have "Calabash is complete" part of the criteria for that page's dismissal. That would allow me to notify the things that communicate with hardware it's OK for them to progress.
A delay works, but is inelegant. I have to guess how long, and environmental changes could make this problem rear its head again.