Try to break out install method to emit separate 'installed' and 'launched' events to know if the app was installed but user needs to manually launch it. #43
Before we had a single 'installed' event we emitted for windowslib#install. This PR is aiming to break into two separate 'installed' and 'launched' events we emit. The method callback are fired when we do 'installed' event.
This is an attempt to be more granular here so we can know if the app install was successful but only launching it for the user failed (which occurs every time for my Windows 10 mobile device) - so that we don't fail the entire build/run and spit out a message to the user that they'll need to launch the app manually.
Before we had a single 'installed' event we emitted for windowslib#install. This PR is aiming to break into two separate 'installed' and 'launched' events we emit. The method callback are fired when we do 'installed' event. This is an attempt to be more granular here so we can know if the app install was successful but only launching it for the user failed (which occurs every time for my Windows 10 mobile device) - so that we don't fail the entire build/run and spit out a message to the user that they'll need to launch the app manually.