刷紧急委托时，更换舰船装备会卡在装备界面报错

[wuhu128]

在提问之前...

• [x] 我已经搜索了现有的 issues
• [x] 我在提问题之前至少花费了 5 分钟来思考和准备
• [x] 我已经阅读了 Wiki 中的 常见问题(FAQ)
• [x] 我正在使用最新版的 Alas

描述你的问题

刷紧急委托时，更换舰船装备会卡在装备界面报错

如何复现

1. 运行刷紧急委托，选择更换舰船及装备
2. 达到更换装备条件，ALAS运行RECORD FLAGSHIP EQUIPMENT
3. 卡在装备界面
4. 出现问题

预期行为

修复该问题，正常更换装备

相关 Logs

─────────────────────────── RECORD FLAGSHIP EQUIPMENT ────────────────────────────
INFO     19:14:10.305 │ RECORD FLAGSHIP EQUIPMENT                                 
INFO     19:14:10.308 │ <<< UI CLICK >>>                                          
INFO     19:14:10.323 │ Click ( 976,  667) @ FLEET_DETAIL                         
INFO     19:14:10.707 │ Click ( 139,  372) @ FLEET_DETAIL_ENTER_FLAGSHIP          
INFO     19:14:11.098 │ RECORD EQUIPMENT                                          
INFO     19:14:11.101 │ SHIP_SIDE_NAVBAR set to right=1 bottom=1                  
INFO     19:14:11.105 │ Nav item active: 4 from range (0, 4)                      
INFO     19:14:11.109 │ <<< UI CLICK >>>                                          
INFO     19:14:11.313 │ Click ( 992,  155) @ EQUIP_INFO_BAR_3_0                   
INFO     19:14:11.703 │ <<< UI CLICK >>>                                          
INFO     19:14:11.725 │ Click ( 844,  649) @ UPGRADE_ENTER                        
INFO     19:15:11.786 │ Function calls:                                           
                    <string>   L1 <module>                                        
                    spawn.py L105 spawn_main()                                    
                    spawn.py L118 _main()                                         
                  process.py L297 _bootstrap()                                    
                  process.py  L99 run()                                           
          process_manager.py L166 run_process()                                   
                     alas.py L555 loop()                                          
                     alas.py  L69 run()                                           
                     alas.py L408 gems_farming()                                  
             gems_farming.py L432 run()                                           
             gems_farming.py L124 flagship_change()                               
         equipment_change.py  L67 ship_equipment_record_image()                   
                       ui.py L108 ui_click()                                      
                   device.py L188 screenshot()                                    
                   device.py L250 stuck_record_check()                            
                   device.py  L43 show_function_call()                            
WARNING  19:15:11.794 │ Wait too long                                             
WARNING  19:15:11.795 │ Waiting for {'UPGRADE_ENTER', 'UPGRADE_ENTER_CHECK'}      
INFO     19:15:11.931 │ [Package_name] com.bilibili.azurlane                      
ERROR    19:15:11.933 │ GameStuckError: Wait too long                             
WARNING  19:15:11.934 │ Saving error: ./log/error/1763205311934                   
WARNING  19:15:12.475 │ Game stuck, com.bilibili.azurlane will be restarted in 10 
         seconds                                                                  
WARNING  19:15:12.478 │ If you are playing by hand, please stop Alas              
INFO     19:15:12.480 │ Task call: Restart                                        
INFO     19:15:12.492 │ Bind task ['General', 'Alas', 'TaskBalancer',             
         'EventGeneral', 'GemsFarming']                                           
INFO     19:15:12.494 │ Save config ./config\alas.json,                           
         Restart.Scheduler.NextRun=datetime.datetime(2025, 11, 15, 19, 15, 12),   
         Restart.Scheduler.Enable=True                                            
INFO     19:15:22.508 │ Scheduler: End task `GemsFarming`                         
CRITICAL 19:15:22.510 │ Task `GemsFarming` failed 3 or more times.                
CRITICAL 19:15:22.512 │ Possible reason #1: You haven't used it correctly. Please 
         read the help text of the options.                                       
CRITICAL 19:15:22.514 │ Possible reason #2: There is a problem with this task.    
         Please contact developers or try to fix it yourself.                     
CRITICAL 19:15:22.517 │ Request human takeover                                    
INFO     19:15:22.715 │ No provider specified, skip sending

截图

还有别的吗？

No response