iOS Exception: "Dropbox client already authorized"

In the emulator I selected a different device, which causes the iOS to reboot.  Then the error went away.  So perhaps the exception was a side-effect of stoping the app with Xcode and starting it up again.  But that leads me to wonder if there aren't some scenarios in real devices where something like this happens and an inconsistency is generated.  In that case I would like to know what addition steps I can take when starting an OAuth to ensure this exception will not occur.  I cannot use the presence or absence of a stored Access Token, but my data state might be inconsistent with the Dropbox system and I might not have a stored Access Token even though the SDK thinks I should have one.

**** Edit: I tried rebooting the emulator and the exception in OAuth remains.  There is something persistent in the iOS the remembers there was a successful authorization, but it has nothing to do with my app.  I just saw [DropboxClientsManager unlinkClients]; in the example app.  Will this do it, and is it safe and reasonable to call this every time, just before authorizeFromController, even if there is no existing authorized client?