Log at Building Failed

Skipped building RxKeyboard due to the error:
Dependency "RxKeyboard" has no shared framework schemes for any of the platforms: iOS

Building the framework throws the following error: Incompatible Swift version - framework was built with 4.0.3 (swiftlang-900.0.74.1 clang-900.0.39.2) and the local version is 4.2 (swiftlang-1000.11.37.1 clang-1000.11.45.1).

Which is weird because the project is updated to Swift 4.2

I am trying to build my project using Xcode 10 and swift 4.2 with iOS Deployment Target set to iOS 10.0.

I got RxKeyboard at version 0.9.0 using Carthage.

This is the error message I get at the import RxKeyboard line when I try to build for simulator:

Module file's minimum deployment target is ios12.0 v12.0: /Users/<my_username>/<my_folder>/<my_project>/Carthage/Build/iOS/RxKeyboard.framework/Modules/RxKeyboard.swiftmodule/x86_64.swiftmodule

and this is the error message I get when I try to build for iPhone X real device:

Module file's minimum deployment target is ios12.0 v12.0: /Users/<my_username>/<my_folder>/<my_project>/Carthage/Build/iOS/RxKeyboard.framework/Modules/RxKeyboard.swiftmodule/arm64.swiftmodule

Does that mean I cannot use this lib if I want to support iOS 10.0 ?

Currently FRAMEWORK_SEARCH_PATHS is set to $(PROJECT_DIR)/Carthage/Build/iOS. This gives a warning when building from source in a consuming workspace:

ld: warning: directory not found for option '-F/Users/bejones/Development/project/Carthage/Checkouts/RxKeyboard/Carthage/Build/iOS'

The correct setup is to not have this and to include RxSwift in the Workspace and use Xcode's Implicit Dependency Management. That way it knows how to compile both as a part of Carthage and in the workspace for development: https://www.quora.com/How-should-an-OSS-library-be-structured-for-distribution-with-both-Carthage-and-CocoaPods/answer/Justin-Spahr-Summers

RxKeybaord doesn't compile on newest Xcode 10 beta

Incompatible Swift version - framework was built with 4.1.2 (swiftlang-902.0.54 clang-902.0.39.2) and the local version is 4.2 (swiftlang-1000.0.32.1 clang-1000.10.39).

Swift version

Apple Swift version 4.0 (swiftlang-900.0.65.2 clang-900.0.37) Target: x86_64-apple-macosx10.9

Carthage version

0.26.2

Cartfile

github "RxSwiftCommunity/RxKeyboard" ~> 0.7

console

$carthage update --platform iOS

result

*** Skipped building RxKeyboard due to the error: Dependency "RxKeyboard" has no shared framework schemes for any of the platforms: iOS

If you believe this to be an error, please file an issue with the maintainers at https://github.com/RxSwiftCommunity/RxKeyboard/issues/new

I tried to run a application then I got a following error message.

dyld: Library not loaded: @rpath/RxCocoaRuntime.framework/RxCocoaRuntime Referenced from: /Users/yuri/Library/Developer/CoreSimulator/Devices/~~~/Yuri.app/Frameworks/RxKeyboard.framework/RxKeyboard Reason: image not found

It seems RxKeyboard refers RxCocoaRuntime.

Hi, I'm using Xcode 9.3 beta 4 with Swift 4.1 and carthage for my dependencies.

Please can you provide a binary compiled with the latest version of Xcode 9.3 for carthage ?

Thanks

I think we should use a weak reference (not a strong) in our examples. By default, and when we use square brackets without explicitly specifying the type of reference, Swift uses a strong reference to external objects.

I understand that this code is provided just to "show the concept". But i don't think it's rational argument to give user incorrect code with memory leak. Imagine someone copy-pasted it and get leaked viewController.

I didn't add guard let 'self' = self else { return } to keep code short.

Hi!

This commit bumps the iOS and tvOS versions to use when using Travis CI.

But, we have to be very careful here since Swift 4.1 and Xcode 9.3 cause runtime issues with RxSwift. Please see: https://github.com/ReactiveX/RxSwift/issues/1555

Thanks!

Bumps tzinfo from 1.2.9 to 1.2.10.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Looks like RxKeyboard has the wrong behavior when we have inputAccessory view. Because willShowVisibleHeight will not trigger on the keyboard because once it was triggered only on inputAccessory view. Same to isHidden

Bumps cocoapods-downloader from 1.4.0 to 1.6.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Hi, I am getting a bit strange (unusuable results) for this:

RxKeyboard.instance.visibleHeight
         .drive(onNext: { [weak postCommentContainerConstraint] keyboardVisibleHeight in
             print("Keyboard visible height \(keyboardVisibleHeight)")
             
             self.view.setNeedsLayout()
             UIView.animate(withDuration: Constants.kCommentBoxAnimationDuration) {
                 
                 postCommentContainerConstraint?.constant = keyboardVisibleHeight
                     self.view.layoutIfNeeded()
                   }
         })

postCommentContainerConstraint is constraint that defines distance between custom view bottom and a container view bottom. If I hardcode value, it works as it should. A pic from storyboard:

the output is:

Keyboard visible height 291.0 Keyboard visible height 335.0 Keyboard visible height 0.0 Keyboard visible height 335.0 Keyboard visible height 0.0 Keyboard visible height 335.0 Keyboard visible height 0.0 Keyboard visible height 335.0

The thing is the actual visible height of a keyboard (along with a toolbar) is around 260.

Why I am getting different and wrong values?

My current setup is, I have a tabbar, and a tableview. Over the tableview I have a custom view with a textView. I want to slide it up and down as keyboard shows/hides.

What am I doing wrong?

Currently, the keyboard only start kick start keyboard dismiss interactively operation when drag down operation touching keyboard edge.

However, in WhatsApp app, the keyboard dismiss operation will kick start, when the drag operation touches the bottom bar edge, even before touching keyboard edge.

Does anyone have idea what is the technique used by WhatsApp, to achieve such behavior? Thanks.