nRF Connect IOS / Android differences ??

[Flemming Jensen]

Hi,

I have a board that emits 0x1818 (Cycling Power) using the nrf51422 chip and firmware using S310 and so forth. Working great :)

Now I just found some strange things going on.

If I browse the device (and other devices fx my spartan watch, hr monitors) using nRF Connect i can see a list of services fx 0x1800, 0x1801, 0x180a, 0x180f, 0x1818

That is all fine.

If I use nRF Connect on my IPAD i get the same services list but two namely: 0x1800, 1801???

Why is 1800 and 1801 missing on the ipad?

Now the problem.

I have developed an app using Cordova where I might write to the 0x1800 service.

This is working fine on Android but on IOS i get service 0x1800 is not found???

Is IOS somehow just filtering access to 0x1800 and 0x1801 out??

A bit confused I must say

[run_ar]

iOS doesn't give the application access to modify the generic access services. e.g.device name. So if you need to update this from iOS you could use a custom characteristic to do this.

[kobyatom]

is still the case in 2020?

[run_ar]

I have not checked lately, but most likely it is still the case. Look at the core bluetooth api's to see what is supported and not.