Question

I am working on an app that uses location services. If I am debugging, the app works fine. If I start without debugging, on the first run (after rebuild), it crashes when asking for authorization to use location services. What happens is that if you let it sit, with the messagebox showing long enough (5-10 seconds), it crashes. If I start without debugging again, it works fine (though it doesn’t show the messagebox again, because somehow it gets past that line to the next line AFTER the conditional statement, where it sets first run false (I assume, because it doesn’t show again).

Again, if I am debugging, no problems. If I start without debugging, it dies. This is the case when building in either the Debug or Release modes.

If I comment this block of code out, it executes without a problem. If I click OK quickly, it executes without a problem.

 if (settings.FirstRunLocationPermission)
              {
                    string message = "Do you wish to use location services to see your location on the map? Your location is not being tracked. You can change this authorization in the settings.";
                    //if (MessageBox.Show(message,"authorization",MessageBoxButton.OKCancel) == MessageBoxResult.OK)
                    //{
                    //      settings.AllowLocation = true;
                    //}
                    settings.FirstRunLocationPermission = false;
              }

I would greatly appreciate it if anyone can explain to me why a simple messagebox checking for ok would cause a problem like this. Thanks!

Answer 1

If you look at the MSDN Documentation for the method, the reasons for the possible Exceptions is fairly clear:

MDSN – MessageBox.Show Method

The other possibility is that there is some code running in the setter for the settings.AllowLocation property that is throwing the Exception. It would help if you included the actual Exception being thrown.