Flutter应用运行正常但出现多类日志错误,疑涉网络连接问题
Flutter应用重置时的日志问题分析与解决
先贴出完整的重置日志供参考:
Performing hot restart... Syncing files to device sdk gphone64 arm64... Restarted application in 846ms. I/flutter ( 7324): User is not logged yet D/EGL_emulation( 7324): app_time_stats: avg=27994.54ms min=27994.54ms max=27994.54ms count=1 I/flutter ( 7324): user is already logged in yet W/DynamiteModule( 7324): Local module descriptor class for com.google.android.gms.providerinstaller.dynamite not found. I/DynamiteModule( 7324): Considering local module com.google.android.gms.providerinstaller.dynamite:0 and remote module com.google.android.gms.providerinstaller.dynamite:0 W/ProviderInstaller( 7324): Failed to load providerinstaller module: No acceptable module com.google.android.gms.providerinstaller.dynamite found. Local version is 0 and remote version is 0. I/flutter ( 7324): user is already logged in yet D/TrafficStats( 7324): tagSocket(120) with statsTag=0xffffffff, statsUid=-1 I/flutter ( 7324): user is already logged in yet D/EGL_emulation( 7324): app_time_stats: avg=432.94ms min=27.87ms max=1386.56ms count=5 W/Firestore( 7324): (24.2.2) [OnlineStateTracker]: Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds W/Firestore( 7324): W/Firestore( 7324): This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend. D/TrafficStats( 7324): tagSocket(120) with statsTag=0xffffffff, statsUid=-1
各日志问题拆解与修复方案
1. D/TrafficStats( 7324): tagSocket(120) with statsTag=0xffffffff, statsUid=-1
这是Android系统的调试日志,不是应用错误。它只是系统在标记Socket连接用于流量统计,特殊值说明该连接未被归类到特定统计标签,完全不影响应用功能,不用处理。
2. user is already logged in yet 重复触发
这是你自己的业务日志,说明登录状态检查逻辑存在重复调用问题:
- 排查代码中登录状态的监听逻辑,比如全局状态管理(Provider/Riverpod/Bloc)、
initState或didChangeDependencies中是否重复注册了状态回调; - 检查热重启时状态是否未被正确重置,导致多次触发判断逻辑;
- 梳理登录流程,确保状态检查方法只在必要时机调用一次。
3. ProviderInstaller相关警告
这类日志和Google Play服务的安全证书更新模块有关,会影响SSL连接的有效性:
- 模拟器环境:检查模拟器的Google Play服务是否安装并更新到最新版本,部分旧版本模拟器自带的服务版本过低;
- 真机环境:确保设备已安装Google Play服务,且版本满足Firebase依赖要求;
- 可在
android/app/build.gradle中手动添加依赖:
同步gradle后重新运行应用。implementation 'com.google.android.gms:play-services-basement:18.2.0' implementation 'com.google.android.gms:play-services-auth:20.7.0'
4. Firestore连接失败警告
这是核心网络问题,直接导致Firestore无法正常同步:
- 先确认设备(模拟器/真机)网络正常,能访问外网;
- 检查Firebase控制台中应用的SHA-1指纹是否配置正确,
google-services.json是否放在android/app目录下; - 临时放宽Firestore安全规则(开发阶段),排除权限问题;
- 模拟器测试时,尝试切换到真机验证,部分模拟器的网络代理或DNS配置会阻止Firestore连接;
- 检查本地防火墙或代理是否拦截了HTTPS端口443的请求(Firestore依赖该端口)。
内容的提问来源于stack exchange,提问作者user17281101
相关产品推荐
相关产品推荐

