Skip to content

iOS simulator unavailable, device type profile not found #97303

Closed

Description

@jmagman

Try job module_test_ios trying to create a simulator:

[module_test_ios] [STDOUT] Executing "xcrun simctl create TestAdd2AppSim com.apple.CoreSimulator.SimDeviceType.iPhone-11 com.apple.CoreSimulator.SimRuntime.iOS-14-3" in "/opt/s/w/ir/x/w/recipe_cleanup/tmp81ddsf_o/flutter sdk" with environment {BOT: true, LANG: en_US.UTF-8}
[module_test_ios] [STDOUT] stderr: Invalid device type: com.apple.CoreSimulator.SimDeviceType.iPhone-11

List of simulators shows all the simulators are "unavailable, device type profile not found"

-- iOS 13.0 --
    iPad Air (3rd generation) (C657E8D4-422B-4449-94E7-3B04431E2F18) (Shutdown) (unavailable, device type profile not found)
    iPad Pro (11-inch) (C3480239-0A68-47BF-97E9-20CFDA93F7D9) (Shutdown) (unavailable, device type profile not found)
    iPad Pro (12.9-inch) (3rd generation) (19F3AE1E-AFAB-447B-9AF6-7B8BB57D9897) (Shutdown) (unavailable, device type profile not found)
    iPad Pro (9.7-inch) (117D9CD0-82C8-458D-B3C4-8CA0331A03AD) (Shutdown) (unavailable, device type profile not found)
    iPhone 11 (6B11A7F3-E077-42F1-9911-D7C1B8D55CCE) (Shutdown) (unavailable, device type profile not found)
    iPhone 11 Pro (2E9AD3C2-AEE6-4152-A14F-882F3DFFDF91) (Shutdown) (unavailable, device type profile not found)
    iPhone 11 Pro Max (8C49B646-040E-4CB6-9FDC-10362CEB54B1) (Shutdown) (unavailable, device type profile not found)
    iPhone 8 (5DCC7E66-B73E-463A-A91D-F28E3B4E329B) (Shutdown) (unavailable, device type profile not found)
    iPhone 8 Plus (18E32AAD-47C2-424D-8A9E-7BFEEA4727A1) (Shutdown) (unavailable, device type profile not found)

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8823963857735512193/+/u/list_simulators/stdout

Compare to a successful prod run. Both are running 12c33.

-- iOS 13.0 --
    iPhone 8 (D6D03B46-EA7B-4A19-9115-6DB597FCF8B6) (Shutdown) 
    iPhone 8 Plus (D23E78A6-2A7F-410D-91FD-2D6779CC411B) (Shutdown) 
    iPhone 11 (3ACE52C8-0530-491A-9226-6A95068DFEF8) (Shutdown) 
    iPhone 11 Pro (6C3DB249-0409-4726-BABB-8BF3417E3E12) (Shutdown) 
    iPhone 11 Pro Max (98B27E12-DECA-41F3-AD22-530C3FE08CC9) (Shutdown) 
    iPad Pro (9.7-inch) (9A5CB7DA-3709-4970-BA8E-A359F60F2A2C) (Shutdown) 
    iPad Pro (11-inch) (EB1BBB3C-9519-4976-B394-D5E3F1C81455) (Shutdown) 
    iPad Pro (12.9-inch) (3rd generation) (420854E4-EE4A-4962-AE41-157DF43EA734) (Shutdown) 
    iPad Air (3rd generation) (4DEB6175-773A-45C8-A791-AF125666FDD9) (Shutdown) 

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8823956734184440353/+/u/list_simulators/stdout

Blocking the plugin roll #97295, which is blocking an engine roll.

Activity

  1. added
    team-infraOwned by Infrastructure team
    P0Critical issues such as a build break or regression
    on Jan 26, 2022
  2. jmagman commented on Jan 26, 2022

    @jmagman
    MemberAuthor

    Re-running the test in #97295, I don't see it failing in other PRs (that PR is definitely not the issue though)

  3. jmagman commented on Jan 26, 2022

    @jmagman
    MemberAuthor

    Suspect the re-run will succeed, the simulator list looks correct:

    -- iOS 13.0 --
        iPhone 8 (96198A19-44E4-4FAB-8516-DD50D00289BF) (Shutdown) 
        iPhone 8 Plus (91CF9D98-4DBC-4451-A823-A0A5B8A59EC6) (Shutdown) 
        iPhone 11 (D6B26EFF-F0AC-4071-A061-94336006AC33) (Shutdown) 
        iPhone 11 Pro (B03469C1-55BD-4B36-BD88-A082F905115B) (Shutdown) 
        iPhone 11 Pro Max (16B9D00E-E5F5-42E1-B5F7-C5B78458BFF0) (Shutdown) 
        iPad Pro (9.7-inch) (C19AAD9E-F393-4AEE-86B0-D3B99F6CAFD2) (Shutdown) 
        iPad Pro (11-inch) (B4B9BB52-BFE4-422D-8B5E-B06A759E3FEB) (Shutdown) 
        iPad Pro (12.9-inch) (3rd generation) (07FC72C6-605D-4A1D-ACB6-A1FF09BA7D09) (Shutdown) 
        iPad Air (3rd generation) (E552B27C-FDCD-4228-B33E-74C9A8207A54) (Shutdown)
    

    https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8823953796628412001/+/u/list_simulators/stdout

    Reducing priority.

  4. added and removed
    P0Critical issues such as a build break or regression
    on Jan 26, 2022
  5. jmagman commented on Jan 26, 2022

    @jmagman
    MemberAuthor

    I've seen that unavailable, device type profile not found before while investigating #91689 when simulator runtimes were missing, but the runtimes look correct this time:

    == Runtimes ==
    iOS 13.0 (13.0 - 17A577) - com.apple.CoreSimulator.SimRuntime.iOS-13-0
    iOS 14.3 (14.3 - 18C61) - com.apple.CoreSimulator.SimRuntime.iOS-14-3
    watchOS 6.1 (6.1.1 - 17S445) - com.apple.CoreSimulator.SimRuntime.watchOS-6-1
    watchOS 7.2 (7.2 - 18S561) - com.apple.CoreSimulator.SimRuntime.watchOS-7-2
    
  6. jmagman commented on Jan 26, 2022

    @jmagman
    MemberAuthor

    And interestingly only the 14.3 iPhone 12* devices are available...?

    == Device Types ==
    iPhone 12 mini (com.apple.CoreSimulator.SimDeviceType.iPhone-12-mini)
    iPhone 12 (com.apple.CoreSimulator.SimDeviceType.iPhone-12)
    iPhone 12 Pro (com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro)
    iPhone 12 Pro Max (com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro-Max)
    ...
    -- iOS 14.3 --
        iPhone 12 mini (5B76E7EE-4109-4327-BD3C-08B088482192) (Shutdown) 
        iPhone 12 (5F6A55BC-C974-4D3B-AC0F-B92F55ED1AD6) (Shutdown) 
        iPhone 12 Pro (E7FEF58E-626E-4EFB-AE6A-5CB49FCE6321) (Shutdown) 
        iPhone 12 Pro Max (787AB908-C531-44CD-9530-524CCA545D60) (Shutdown)
    

    https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8823963857735512193/+/u/list_simulators/stdout

  7. CaseyHillers commented on Jan 26, 2022

    @CaseyHillers
    Contributor

    I'll monitor the builds to see if this flake occurs again

  8. self-assigned this
    on Jan 26, 2022
  9. godofredoc commented on Jan 27, 2022

    @godofredoc
    Contributor

    Waiting for the battery healthcheck to land in production.

  10. jmagman commented on Jan 27, 2022

    @jmagman
    MemberAuthor

    I don't think this is related to the tethered device's health, it's that the simulators aren't set up in a way Xcode can find them.

  11. godofredoc commented on Jan 28, 2022

    @godofredoc
    Contributor

    Would this be fixed with the new way to provide runtimes?

  12. 61 remaining items

  13. CaseyHillers commented on Mar 30, 2022

    @CaseyHillers
    Contributor

    Talked with @yjbanov and it seems like Mac Web Engine is running on Mac 12 now. We landed flutter-team-archive/engine#32337 as the issue is running this test on the corrupt Mac 10 bots.

  14. jmagman commented on Mar 30, 2022

    @jmagman
    MemberAuthor

    Talked with @yjbanov and it seems like Mac Web Engine is running on Mac 12 now. We landed flutter/engine#32337 as the issue is running this test on the corrupt Mac 10 bots.

    This builder failed many times on Xcode 13 due to #99885 /cc @godofredoc it passed a few times for reasons we couldn't figure out.

  15. keyonghan commented on Mar 30, 2022

    @keyonghan
    Contributor

    The latest build is hanging. I guess we need a revert: flutter-team-archive/engine#32340
    Meanwhile, I am cleaning up caches.

  16. godofredoc commented on Mar 30, 2022

    @godofredoc
    Contributor

    I have some local changes I used for validation yesterday unfortunately I haven't been able to test them yet. I'll upload the current version of the recipe change just in case someone has free cycles to validate it.

  17. godofredoc commented on Mar 30, 2022

    @godofredoc
    Contributor

    Here is a run with the changes to remove the runtimes properly: https://chromium-swarm.appspot.com/task?id=59f5766358a6e610

  18. keyonghan commented on Mar 30, 2022

    @keyonghan
    Contributor

    All bots are cleaned up, and we should be ready to land flutter-team-archive/engine#32340 to unblock the tree.

  19. CaseyHillers commented on Mar 31, 2022

    @CaseyHillers
    Contributor

    After 15+ green runs, this looks fixed. Thanks Keyong!

  20. github-actions commented on Apr 14, 2022

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  21. locked as resolved and limited conversation to collaborators on Apr 14, 2022
  22. moved this from Verified to To be archived in [DEPRECATED] Infra Ticket Queueon Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P0Critical issues such as a build break or regressionc: flakeTests that sometimes, but not always, incorrectly passteam-infraOwned by Infrastructure team

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions