Bliss Wetchaya

Facing this issue for 2 weeks now.

> @jaspervp how to downgrade fastlane to that version? @SwiftiSwift If you are using `bundle` to run fastlane. You can specify in Gemfile ``` # Gemfile gem "fastlane", "~> 2.197.0"...

I've seen all kind of fixes to this similar problem. Read all issues related and @canturkm fixes my. Cheers

You can use `is_key_content_base64` from [fastlane. app_store_connect_api_key](https://docs.fastlane.tools/actions/app_store_connect_api_key/) which does not show the same error as the non-base64 version. ``` app_store_connect_api_key( key_id: "D83848D23", issuer_id: "227b0bbf-ada8-458c-9d62-3d8022b7d07f", key_content: "Base64_encode_of_-----BEGIN EC PRIVATE KEY-----\nfewfawefawfe\n-----END EC...

@markgravity I am wondering if this is related to tuist folder naming bug and is fixed in #514 🤔

Pods successfully build but when run on M1 iOS Simulator results in `error build: Building for iOS Simulator, but linking in dylib built for iOS, file '/Pods/Alamofire/_Prebuilt/Alamofire.framework/Alamofire' for architecture arm64`

Here is my working settings in `podfile` ``` config_cocoapods_binary_cache( cache_repo: { "default" => { "local" => "~/.cocoapods-binary-cache/prebuilt-frameworks" } }, prebuild_config: "PodCache", device_build_enabled: true, build_args: { :simulator => [ "ARCHS='x86_64 arm64'"...

This works well for replacing with one screen.

@Shayokh144 This looks like a feature because we didn't support it before 🤔 Should we change it to `feature`?

I'm getting this same failure on Intel Mac as well. Xcode: 14.2 (14C18) Mac: 12.5 (21G72). ``` Prebuild frameworks (total 22) Prebuilding Firebase Prebuilding KeychainAccess... Done ```