终于想通了事情的原委，并听取了关于颌骨回来。事实证明，它们对后端碰撞，如果你使用相同的权威性与两个不同的客户。

Finally figured out what was going on and heard back from Jawbone about it. It turns out that they have collisions on the backend if you use the same auth with two different clients.

有关别人运行到这个问题，不要在两个不同的上下文中同时使用同一个登录名，因为它会在怪异的方式重新AUTHS。

For anyone else that runs into this problem, don't use the same login in two different contexts simultaneously as it will reset auths in weird ways.

在我们的例子中，我们有一个经常被开发者之间共享，因为它有时是很难获得真实的数据，除非你有实际设备测试用户帐户。这是导致该做的Jawbone code怪胎了'重复'登录。

In our case, we have test user accounts that are often shared between devs since it is sometimes hard to get real data unless you have the actual device. This was causing 'duplicate' logins that made Jawbone code freak out.

我们得到了确认从Jawbone的开发制定一个内部应用程序时，谁碰到了同样的问题.....

We got confirmation from a Jawbone dev who ran into the same problem when developing an internal app.....