规格（新）
Flutter version 3.13.2
JDK version 17.0.6+0
Dart version 3.1.0
规格（旧）
Flutter version (idk much about it but i think it is on 3.3.3)
JDK version (unknown)
Dart version (I think it is on dart 2)
这个项目是我从我的合作伙伴那里得到的，他们需要从旧版本到新版本进行一些维护并添加一些地图页面，但是发生了一些事情，当我运行应用程序时，我得到了它和终端的延迟说“Hang State”或者类似的东西，说实话有很多警告，我不知道我能做什么以及问题出在哪里
这些是终端对话框的摘要
W/MIUIScout App(31798): Enter APP_SCOUT_WARNING State
W/MIUIScout App(31798): Event:APP_SCOUT_WARNING Thread:main backtrace:
W/MIUIScout App(31798): at jdk.internal.misc.Unsafe.park(Native Method)
W/MIUIScout App(31798): at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
W/MIUIScout App(31798): at
com.wongpiwat.trust_location.LocationAssistant.checkInitialLocation(LocationAssistant.java:494)
com.google.android.gms.common.api.internal.BasePendingResult$CallbackHandler.handleMessage(com.google.android.gms:play-services-base@@18.1.0:6)
I/e.mobilebenerit(31798): Wrote stack traces to tombstoned
W/MIUIScout App(31798): Enter APP_SCOUT_HANG state
W/MIUIScout App(31798): (Current message: duration=5003ms seq=31 late=4ms h=com.google.android.gms.common.api.internal.BasePendingResult$CallbackHandler w=1)
D/AppScoutStateMachine(31798): dump trace dirName = com.example.mobilebenerit-31798-APP_SCOUT_HANG-2023-10-13-10-34-24
W/MIUIScout App(31798): Event:APP_SCOUT_HANG Thread:main backtrace:
W/MIUIScout App(31798): at jdk.internal.misc.Unsafe.park(Native Method)
W/MIUIScout App(31798): at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
W/MIUIScout App(31798): at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:717)
W/MIUIScout App(31798): at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1074)W/MIUIScout App(31798): at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:276)
W/MIUIScout App(31798): at com.wongpiwat.trust_location.LocationAssistant$8.onResult(LocationAssistant.java:722)
W/MIUIScout App(31798): at com.google.android.gms.common.api.internal.BasePendingResult$CallbackHandler.handleMessage(com.google.android.gms:play-services-base@@18.1.0:6)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:559)
W/MIUIScout App(31798): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:954)
I/e.mobilebenerit(31798): Thread[5,tid=31817,WaitingInMainSignalCatcherLoop,Thread*=0xb400007ab1d6d000,peer=0x134c4600,"Signal Catcher"]: reacting to signal 3
I/e.mobilebenerit(31798):
I/e.mobilebenerit(31798): Wrote stack traces to tombstoned
W/Looper (31798): PerfMonitor longMsg : seq=31 plan=10:34:19.957 late=4ms wall=30006ms running=5ms runnable=1ms h=com.google.android.gms.common.api.internal.BasePendingResult$CallbackHandler w=1 procState=-1
I/Choreographer(31798): Skipped 1815 frames! The application may be doing too much work on its main thread.
W/Looper (31798): PerfMonitor doFrame : time=0ms vsyncFrame=0 latency=29994ms procState=-1 historyMsgCount=1 (msgIndex=1 wall=30006ms seq=31 running=5ms runnable=1ms late=4ms h=com.google.android.gms.common.api.internal.BasePendingResult$CallbackHandler w=1)
我尝试从错误或警告信息中解决一些问题 flutter 并升级 pubspec.yaml 中的 bug 和错误，并将 dep 升级到新版本，除了 http 和 one_signal 以及与之相关的内容（http : 0.13.6, onesignal_flutter: ^3.2.8）
有什么我需要升级请告诉我
问题在于使用了其中一种方法或可能是“trust_location”包中的变量，请尝试再次检查。如果确实该包有问题，请考虑用类似的包替换它。