Broken NUS after iOS 10 upgrade

RE: Broken NUS after iOS 10 upgrade

Mostafa Berg — Wed, 12 Apr 2017 12:16:24 GMT

This has been fixed, as you can see the issue here

At the time of writing, the current version on the app store is v4.4.1

You may download that or compile the source and UART will be fully functional again.

Sorry about the inconvenience, let us know if you need any help

RE: Broken NUS after iOS 10 upgrade

Tim — Tue, 25 Oct 2016 14:42:52 GMT

I apologize for my negligence in specifying that I had already created a devzone question when I submitted the mypage issue; I will do so in the future. Thank you for all the quick responses!

RE: Broken NUS after iOS 10 upgrade

run_ar — Tue, 25 Oct 2016 09:14:21 GMT

I recreated your problem. Looks like an issue with nRF toolbox as it works with the old nRF UART app I use for testing sometimes. I have registered this in our internal bug tracking system. The iOS devs will look at it in their next sprint planning. For now I suggest you use a different app for testing.

Note: please notify us when creating duplicate cases in both devzone and mypage. Or avoid creating duplicates all togheter... Thanks!

RE: Broken NUS after iOS 10 upgrade

run_ar — Tue, 25 Oct 2016 07:44:10 GMT

Looks like we already have an issue for this. I Have talked to the developer and they will check if this is an iOS or nRF toolbox issue soon. I'll register an internal issue as well.

RE: Broken NUS after iOS 10 upgrade

run_ar — Tue, 25 Oct 2016 07:18:00 GMT

Did you consider registering this as an issue here: https://github.com/NordicSemiconductor/IOS-nRF-Toolbox

RE: Broken NUS after iOS 10 upgrade

Tim — Mon, 24 Oct 2016 14:38:40 GMT

As I have started to conclude that this is most likely a problem with the nRF Toolkit App and not an issue with my code, I have created a support case on the www.nordicsemi.com webpage. I will update this question when I receive an answer from that avenue.

RE: Broken NUS after iOS 10 upgrade

Tim — Mon, 24 Oct 2016 14:35:51 GMT

I have not been using Xcode for development, so I don't know how to retrieve the device log.

I am using v4.1.1 of nRF Toolkit. For softdevice and SDK, I am using:

C:\Keil_v5\ARM\Pack\NordicSemiconductor\nRF_SoftDevice_S130\2.0.0-7.alpha\hex\s130_nrf51_2.0.0-7.alpha_softdevice.hex
C:\Keil_v5\ARM\Pack\NordicSemiconductor\nRF_Examples\11.0.0-2.alpha\ble_peripheral\ble_app_uart\pca10028\s130\arm5_build\nrf51422_xxac_s130.hex

RE: Broken NUS after iOS 10 upgrade

run_ar — Mon, 24 Oct 2016 14:32:08 GMT

I'm sorry not sure why I wrote type. I was thinking about the nsdata object, but looks like that hasn't changed since iOS 8. Are you getting any error message in the xcode device log? I can see if I can recereate it. Which app version are you using on iOS? Which SDK and Softdevice are you using?

RE: Broken NUS after iOS 10 upgrade

Tim — Mon, 24 Oct 2016 14:23:27 GMT

I am using iOS 10 (10.0.2 (14A456)). The actual message that is transmitted varies regardless of the message sent I attempt to send. Repeated attempts to send "Test" will even yield different results.

As for the "types that is discontinued no iOS 10?", what are you referring to? I am using the standard English keyboard on iOS if that's what you mean.

RE: Broken NUS after iOS 10 upgrade

run_ar — Mon, 24 Oct 2016 10:55:19 GMT

Ok, so you try to send 'test'. But for some reason iOS says you sent '0x17582964' which is also what the peer receives? And this happens all the time with iOS 10.0.x? What happens when you send something else than test? still '0x17582964'?

Can you check that you are not using any types that is discontinued no iOS 10? in case there are any changes.

RE: Broken NUS after iOS 10 upgrade

Tim — Fri, 21 Oct 2016 17:00:58 GMT

Using the sniffer, I was able to see that the messages are being sent correctly, but my iPhone is just not sending the message I specify. For example, When I try to send the message "Test" as it results in a green notification on my iPhone '0x17582964 sent.' similar to the message in the third picture. This is indeed the message sent to the device as sniffed using Wireshark/Nordic Sniffer. Seen by the sniffer, the device in turn responds with the proper "NOT OK" message that it is programmed to, but all I see on my phone is 'Optional(6 bytes) received' as another green notification.

RE: Broken NUS after iOS 10 upgrade

run_ar — Thu, 20 Oct 2016 09:04:02 GMT

What is the return value from sd_ble_gatts_hvx / ble_nus_string_send? It might also be an idea to capture the on air traffic to see what happens using a sniffer.

RE: Broken NUS after iOS 10 upgrade

Tim — Wed, 19 Oct 2016 14:34:20 GMT

The fourth picture was from a few months ago. I have updated the question; see above.

RE: Broken NUS after iOS 10 upgrade

Øyvind Karlsen — Wed, 19 Oct 2016 06:36:21 GMT

Hi,

You send "T" at 15:31:40.212 and receive "49.9,59.7,54.8,3.3,3" at 15:31:40.363. Are these not the values you expect to see?