ReactiveX / RxSwift

Reactive Programming in Swift
MIT License
24.34k stars 4.17k forks source link

Build failed in Xcode12.5 #2311

Closed cacawai closed 3 years ago

cacawai commented 3 years ago

Short description of the issue:

Build failed in Xcode12.5

Expected outcome:

Build without error in Xcode12.5

What actually happens:

screenshot-20210428-143823

RxSwift/RxCocoa/RxBlocking/RxTest version/commit

6.1.0

Platform/Environment

How easy is to reproduce? (chances of successful reproduce after running the self contained code)

Xcode version:

Xcode12.5



:warning: Fields below are optional for general issues or in case those questions aren't related to your issue, but filling them out will increase the chances of getting your issue resolved. :warning:

**Installation method**:
  - [ ] CocoaPods

**I have multiple versions of Xcode installed**:
  (so we can know if this is a potential cause of your issue)
  - [ ] no

**Level of RxSwift knowledge**:
  (this is so we can understand your level of knowledge
    and formulate the response in an appropriate manner)
  - [ ] I have a significant code base
freak4pc commented 3 years ago

Can you please try the main branch directly? We should have a release in the following days.

Thanks, On 28 Apr 2021, 9:48 +0300, 擦擦外 @.***>, wrote:

Short description of the issue: Build failed in Xcode12.5 Expected outcome: Build without error in Xcode12.5 What actually happens: RxSwift/RxCocoa/RxBlocking/RxTest version/commit 6.1.0 Platform/Environment

• iOS

How easy is to reproduce? (chances of successful reproduce after running the self contained code)

• easy, 100% repro

Xcode version: Xcode12.5

:warning: Fields below are optional for general issues or in case those questions aren't related to your issue, but filling them out will increase the chances of getting your issue resolved. :warning:

Installation method:

  • [ ] CocoaPods

I have multiple versions of Xcode installed: (so we can know if this is a potential cause of your issue)

  • [ ] no

Level of RxSwift knowledge: (this is so we can understand your level of knowledge and formulate the response in an appropriate manner)

  • [ ] I have a significant code base — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
hiragram commented 3 years ago

@cacawai Use main branch instead. It is already fixed but not released yet.

cacawai commented 3 years ago

pod 'RxCocoa', :git => 'https://github.com/ReactiveX/RxSwift.git', :branch => 'main' Tried the main branch , still got this error

hiragram commented 3 years ago

Are there any diff in Podfile.lock after pod update ? I'm not sure but I think you should specify branch for every pods from this repository such as pod 'RxSwift'.

cacawai commented 3 years ago

RxCocoa: :commit: 7219024cd02502e9faa6528a655709257f28a105 :git: https://github.com/ReactiveX/RxSwift.git RxSwift: :commit: 7219024cd02502e9faa6528a655709257f28a105 :git: https://github.com/ReactiveX/RxSwift.git

I'm sure using the main branch, and I can see the code that your modified 3 days ago after pod update. but still got this error, and I also tried to clean and rebuild the whole project.

hiragram commented 3 years ago

I have no idea 🤷 Try restarting Xcode or rebooting your mac.

cacawai commented 3 years ago

Reboot doesn't work, I'll use Xcode12.4 now, and continue to work on this issue later.

cacawai commented 3 years ago

I removed $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) from LIBRARY_SEARCH_PATHS in the Build Settings fixed this issue. It's a 9 years old project , I have no idea when and why we add this ...

agruchala commented 3 years ago

@cacawai What version has a fix? 6.1.0?

cacawai commented 3 years ago

@cacawai What version has a fix? 6.1.0?

Yeah, I'm still using version 6.1.0 For me I just removed $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) from LIBRARY_SEARCH_PATHS in the Build Settings. And the build error just disappeared.

agruchala commented 3 years ago

Hmm, for Us it doesn't build on Xcode 12.5 via Carthage, so I think there is a different issue.

kazukisugita commented 3 years ago

@agruchala +1 👍 I'm also facing the same situation... via Carthage