Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Guido Marucci Blas
    @guidomb
    Guido Marucci Blas
    @guidomb
    I’ve just release the first stable version of WLXBluetoothDevice
    Know I am working on a subspec to add ReactiveCocoa support
    *now
    Ryan Brignoni
    @castral
    @guidomb question about ble API, if i attempt to write a characteristic with a block and get a "writing is not permitted" CBATTErrorDomain, should the callback not be called with the error for me to handle? right now i just see "Value for characteristic XXX could not be written: ..." and no callback
    Guido Marucci Blas
    @guidomb
    If you see that log and the callback is not called with the NSError there is a bug
    Ryan Brignoni
    @castral
    i'll dig in and try to figure out why it's not getting called
    Guido Marucci Blas
    @guidomb
    That message comes from WLXServiceManager line 218
    Thanks I will check it too
    Are you getting "Write success notification for characteristic %@ could not be dispatched. There is no registered block"
    Ryan Brignoni
    @castral
    2015-03-20 11:22:22:369 Nima[4876:5117] Trying to write value for characteristic 62A80400-8C10-4A37-B846-EC2BE48E830C
    2015-03-20 11:22:22:369 Nima[4876:5117] Writting value for characteristic 62A80400-8C10-4A37-B846-EC2BE48E830C with response
    2015-03-20 11:22:22:608 Nima[4876:1a07] Value for characteristic 62A80400-8C10-4A37-B846-EC2BE48E830C could not be written: Error Domain=CBATTErrorDomain Code=8 "Writing is not permitted." UserInfo=0x17427f900 {NSLocalizedDescription=Writing is not permitted.}
    Guido Marucci Blas
    @guidomb
    and that is the last log you see?
    Ryan Brignoni
    @castral
    related to that characteristic, yes
    im reading multiple characteristics and writing one in async blocks
    Guido Marucci Blas
    @guidomb
    Can you put a break point in line 222 of WLXServiceManager
    Ryan Brignoni
    @castral
    block is set
    i probably need to expand the macro and trace it
    Guido Marucci Blas
    @guidomb
    the macro dispatches the block in the service queue
    maybe the block does not call because the queue is blocked processing other block
    are you doing some blocking operations inside the callbacks?
    Ryan Brignoni
    @castral
    nope, but i am nesting inside the callback. the write is executed from a callback of a read
    Guido Marucci Blas
    @guidomb
    that should not be a problem
    because the write is actually executed
    Ryan Brignoni
    @castral
    ah ha, this is possibly my own fault
    Guido Marucci Blas
    @guidomb
    OK let me know if you find a bug or you need some help with the library’s code
    I am working on the ReactiveCocoa extension of WLXBluetoothDevice, I have already pushed a 0.2.0-alpha release
    in case you like ReactiveCocoa
    Ryan Brignoni
    @castral
    awesome. sorry yeah i just realized that my nested callback was hiding an earlier declaration
    i am seeing the callback execute correctly on error
    Guido Marucci Blas
    @guidomb
    No problem, let me know if you need anything else
    Ryan Brignoni
    @castral
    thanks for the help
    Guido Marucci Blas
    @guidomb
    I have just found an issue with the reconnection mechanism
    Wolox/WLXBluetoothDevice#27
    Ryan Brignoni
    @castral
    Yeah, I ran into this a couple weeks ago and I just made my client wrapper not reuse managers after disconnect
    didnt think it was an issue in WLXBluetooth tbh
    would be nice if it managed it after reconnect for me, but i didn't find it to be a blocker
    florentilroxxe
    @florentilroxxe
    Hello ! I'm having an issue with the (otherwise fantastic) lib. It seems that it doesn't manage a bluetooth deconnection (when I just deactivate it via the control center on my device). After that the lib doesn't seem to think it's disconnected yet I can't write values to characteristics after that anymore, it just fails without a word. Is that a known issue ? (or no issue at all and I'm just "using it wrong" ;)?)
    *after reactivating bluetooth again
    Guido Marucci Blas
    @guidomb
    I am sorry @florentilroxxe I have just read this message. I the issue still happening? Have you tried with the lastest version in master. (I fixed a couple of bugs and ported it to Carthage)
    Guido Marucci Blas
    @guidomb
    I have release a new version of WLXBluetoothDevice
    Now there is a ReactiveCocoa API!
    I have temporaly dropped CocoaPods support and added Carthage support.