问题描述
突然之间，我们在使用Nest和Firebase进行身份验证时遇到错误.错误代码为9999，并且消息被阻止".应用程序端的源代码未更改，因此服务器端似乎有所更改.
All of a sudden, we are getting an error authenticating with Nest and Firebase. The error code is 9999, and the message is "blocked". The source code has not changed on the app side, so it seems like something has changed on the server side.
在此处，我看到了类似的问题，但是它们越来越消息请求太多"，而不是已阻止".
I see a similar issue here, however they are getting a message of "too many requests", instead of "blocked".
任何人都可以帮助我们解决此问题吗?谢谢.
Can anyone help us resolve this issue? Thanks.
推荐答案
当您使用相同的访问令牌到Nest的并发打开连接过多时，就会发生此错误.与太多请求"问题不同，后者是为了保护恒温器中的电池.
This error occurs when you have too many concurrent open connections to Nest using the same access token. This is a different issue to "too many requests" issue which, as indicated, is to protect the battery in the thermostat.
似乎您可能正在打开Firebase或REST流连接，而在打开新连接之前未正确关闭它们.打开Firebase连接后，您应该使用该连接来读取和写入任何新数据，并且仅在断开连接时才打开新连接.
It seems that you may be opening up Firebase or REST streaming connections and not closing them properly before opening up a new connection. Once a Firebase connection is open you should use this connection for reading and writing any new data and open a new connection only if when this connection is severed.
能否请您发布示例代码来说明如何处理打开，关闭和使用连接?您的示例代码将有助于分析问题的具体情况.
Could you please post sample code on how you are handling opening, closing and using the connections? Your sample code will help analyze the specifics of the issue.
这篇关于Firebase错误代码9999“被阻止"的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！