Unavailable simulator being selected for Snapshot about fastlane

[Wasat1961]

It looks like you're encountering an issue with Fastlane's snapshot action due to the unavailability of a specific simulator device. The error message suggests that the device.plist file for an iPhone 8 Plus simulator is not readable.

To address this issue, you can try the following steps:

You mentioned that you accidentally removed the device data from the CoreSimulator directory. It's possible that the simulator state became inconsistent. You can try cleaning up your simulators using the following Fastlane command:

fastlane snapshot reset_simulators

This command will reset your simulators to a clean state, which may resolve the issue.

Specify the Simulator: You can explicitly specify the simulator you want to use in your Fastfile by adding a devices parameter to your snapshot block. For example:

snapshot(
workspace: "ShopCrate.xcworkspace",
devices: [
"iPhone 8 Plus (02CC7B8D-1BD7-41F7-AAE7-C2F19FB2F5BD)"
],
concurrent_simulators: false,
skip_open_summary: is_ci
)

Replace the device identifier with the one that corresponds to an available simulator.

Update Fastlane: Ensure you are using YourTexasBenefits the latest version of Fastlane by running:

fastlane update_fastlane

Upgrading to the latest version may resolve any known issues related to simulator selection.

Check Simulator Configuration: Verify that the unavailable simulator (with the problematic device.plist) is not explicitly specified or referenced elsewhere in your Fastlane configuration.

Check Xcode Configuration: Ensure that your Xcode installation and configuration are up-to-date and consistent with your project requirements.

Recreate Unavailable Simulator: If none of the above steps work, you might consider recreating the unavailable simulator manually through Xcode's simulator manager. Give it a different name or identifier and then try to specify that in your Fastlane configuration.

If none of these steps resolve the issue, you may need to provide additional context or investigate further into your specific setup, as it could be related to project-specific configuration or a potential bug in Fastlane or Xcode. Additionally, checking the Fastlane GitHub repository for similar issues and solutions may be helpful.

[Zandor300]

Running fastlane snapshot reset_simulators solved the issue.

Thank you bot user for helping me fix my issue. Reported for advertisement.