rxswiftcommunity / rxstarscream Goto Github PK

Hey @rabidaudio I submitting some changes to comply with Swift 3.

As I'm not the owner or have access at Cocoapods, please feel free to submit a new version -> 0.6.

You should add Unit Tests to the repository.

Just annoying, how can I remove it?

Getting this error while doing carthage update

*** Skipped building RxStarscream due to the error:
Dependency "RxStarscream" 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/RxStarscream/issues/new

I tried to do a pod install which resulted in the following:

[!] CocoaPods could not find compatible versions for pod "RxSwift":
  In snapshot (Podfile.lock):
    RxSwift (= 6.1.0)

  In Podfile:
    RxCocoa was resolved to 6.1.0, which depends on
      RxSwift (= 6.1.0)

    RxStarscream was resolved to 0.3, which depends on
      RxSwift (~> 2.5.0)

    RxSwift

My Podfile looks like this:

platform :ios, '10.0'

target 'MyApp' do
	use_frameworks!

	pod 'Firebase/Core'
	pod 'Firebase/Analytics'
	pod 'Firebase/Crashlytics'

	pod 'RxSwift'
	pod 'RxCocoa'

	pod 'RxStarscream'
end

Now,My project use RxSwift 3.5.0 version, which can not be compatible with the version that RxStarscream depends on(~>2.5.0)

You should add Continuous Integration to the repository.

• Swift 4.2 and Xcode 10
• newest RxSwift and Starscream
• readme info about older Swift versions

Getting this error when installing with carthage.

ld: '/xxx/Carthage/Checkouts/RxStarscream/Carthage/Build/iOS/RxTest.framework/RxTest' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture arm64

I've submitted a P.R. to fix this issue: #10

Hello 👋,
I wondering is it possible to use RxStarscream with a serveur on Socket.io ? I know I should use Socket.io swift client but have you already try to make it work without the socket.io swift client ? I manage to connect but I get instant disconnect with code error 1000 but according to the RFC 6455 1000 is like a normal closure. If you have any idea or help to provide I will really appreciate it 😄 !

This was introduced in daltoniam/Starscream#311. Afaict there should be nothing that prevents RxStarscream to replace the dependence on Websocket classes with the protocol, which would make it much easier to write tests.

In README it's under MIT
but in LICENSE file, it's under Apache License

When I tried to run the sample project with just basics to connect web socket, getting this error -Disconnected with optional error : Optional(Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused"

@_exported import RxSwift
@_exported import RxStarscream
import Starscream

  override func viewDidLoad() {
        super.viewDidLoad()
 private let disposeBag = DisposeBag()
 
socket = WebSocket(url: URL(string: "ws://localhost:8080/")!)
        socket.connect()

 socket.rx.response.subscribe(onNext: { (response: WebSocketEvent) in
            switch response {
            case .connected:
                print("Connected")
            case .disconnected(let error):
                print("Disconnected with optional error : \(error)")
            case .message(let msg):
                print("Message : \(msg)")
            case .data(_):
                print("Data")
            case .pong:
                print("Pong")
            }
        }).disposed(by: disposeBag)
}

am I doing anything wrong, I could find the solution..

Pod is not in actual state.
Dependency fix from d716e42 is not applied because spec.version is not changed

Hi,

I'm getting this issue when I run pod update:
RxSwift (~> 2.5.0) required by RxStarscream (0.2)

I am running RxSwift 2.6
Could you please update the dependency.

Best regards,
ZkY.

RxCocoa DelegateProxyType.proxy(for:) need to excute on main scheduler.
What I think RxCocoa is designed for UI operations.

But websocket may not need to force on the main scheduler.