0

我们正在尝试更新我们的 firebase 实时数据库,但更新失败且没有任何回调。使用我们的 android 应用程序的设备很少发生这种情况,我能够在 logcat 中发现这些设备的 firebase 连接失败。

这些日志是使用以下方法生成的: FirebaseDatabase.getInstance().setLogLevel(Logger.Level.DEBUG); 然后被写入文件。

在网上搜索这些日志,我得到了一些提示

  1. android 设备可能已植根
  2. 火力基地问题
  3. 防火墙/安全问题
  4. 网络提供商问题

但是我们无法知道相同的确切根本原因。

谁能提供一些见解或解决方案来解决这个问题?

下面附上日志。

02-17 15:24:26.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:26.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:26.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:26.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:28.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:28.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:28.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:28.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:28.052 E/rm.nobroker.co(19414): failed to connect to jdwp control socket: Connection refused
02-17 15:24:29.435 D/WebSocket(19414): ws_2 - timed out on connect
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closed
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closing itself
02-17 15:24:29.436 D/Connection(19414): conn_2 - Realtime connection failed
02-17 15:24:29.436 D/Connection(19414): conn_2 - closing realtime connection
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Got on disconnect due to OTHER
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Scheduling connection attempt
02-17 15:24:29.436 D/ConnectionRetryHelper(19414): Scheduling retry in 841ms
02-17 15:24:29.435 D/WebSocket(19414): ws_2 - timed out on connect
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closed
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closing itself
02-17 15:24:29.436 D/Connection(19414): conn_2 - Realtime connection failed
02-17 15:24:29.436 D/Connection(19414): conn_2 - closing realtime connection
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Got on disconnect due to OTHER
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Scheduling connection attempt
02-17 15:24:29.435 D/WebSocket(19414): ws_2 - timed out on connect
02-17 15:24:29.436 D/ConnectionRetryHelper(19414): Scheduling retry in 841ms
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closed
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closing itself
02-17 15:24:29.436 D/Connection(19414): conn_2 - Realtime connection failed
02-17 15:24:29.436 D/Connection(19414): conn_2 - closing realtime connection
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Got on disconnect due to OTHER
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Scheduling connection attempt
02-17 15:24:29.436 D/ConnectionRetryHelper(19414): Scheduling retry in 841ms
02-17 15:24:29.435 D/WebSocket(19414): ws_2 - timed out on connect
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closed
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closing itself
02-17 15:24:29.436 D/Connection(19414): conn_2 - Realtime connection failed
02-17 15:24:29.436 D/Connection(19414): conn_2 - closing realtime connection
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Got on disconnect due to OTHER
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Scheduling connection attempt
02-17 15:24:29.436 D/ConnectionRetryHelper(19414): Scheduling retry in 841ms
02-17 15:24:29.435 D/WebSocket(19414): ws_2 - timed out on connect
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closed
02-17 15:24:29.436 D/WebSocket(19414): ws_2 - closing itself
02-17 15:24:29.436 D/Connection(19414): conn_2 - Realtime connection failed
02-17 15:24:29.436 D/Connection(19414): conn_2 - closing realtime connection
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Got on disconnect due to OTHER
02-17 15:24:29.436 D/PersistentConnection(19414): pc_0 - Scheduling connection attempt
02-17 15:24:29.436 D/ConnectionRetryHelper(19414): Scheduling retry in 841ms
4

0 回答 0