Bug Report
Problem
There is a potential race condition problem in activityStart/activityStop, because the former shows the spinner dialog in the UI thread, while the latter hides the spinner dialog in the JS thread. So it is possible for activityStop to try to hide the spinner dialog, while it hasn't event been shown yet, if activityStop is executed immediately (or shortly) after activityStart.
For instance, using the following code (e.g. in Chrome remote debugging console):
navigator.notification.activityStart('', 'Wait...'); navigator.notification.activityStop()
What is expected to happen?
activityStop should always discard a spinner dialog initiated by activityStart.
What does actually happen?
activityStop has no effect, because the spinner dialog hasn't been created yet by activityStart (due to execution in UI thread).
Environment, Platform, Device
Android
Version information
- cordova-android@10
- cordova-plugin-dialogs@2.0.2
Checklist
Bug Report
Problem
There is a potential race condition problem in
activityStart/activityStop, because the former shows the spinner dialog in the UI thread, while the latter hides the spinner dialog in the JS thread. So it is possible foractivityStopto try to hide the spinner dialog, while it hasn't event been shown yet, ifactivityStopis executed immediately (or shortly) afteractivityStart.For instance, using the following code (e.g. in Chrome remote debugging console):
What is expected to happen?
activityStopshould always discard a spinner dialog initiated byactivityStart.What does actually happen?
activityStophas no effect, because the spinner dialog hasn't been created yet byactivityStart(due to execution in UI thread).Environment, Platform, Device
Android
Version information
Checklist