Ios 11.3.1 Creating a EASession with a connected accessory return nil

Creating a EASession with my connected mfi accessory return nil often.

The error states that the session couldnt be close (but no session from code was never opened directly)


The only way we can get a session when this happen is to disconnect the accessory in bluetooth settings and reconnect it.

this problem started with ios 11.3


is this a known bug ?

anybody else encountering this issue ?


thanks

Mat

Doc for initWithAccessory:forProtoco states that :

init?(accessory: EAAccessory, forProtocol protocolString: String)


This method may return nil if the accessory does not recognize the specified protocol or there was an error communicating with the accessory.

Have you checked the protocol you use ?



Could this give some hint ?

h ttps://stackoverflow.com/questions/42117892/closing-easession-issue-external-accessory

the protocol is correct.

our app was working great until ios 11.3

before this version we could always open a session with our connected mfi device.

with 11.3 we see strange behaviours on the mfi connection.

Another behaviour that we never saw before is the streams sometimes showing that they are at the end. When this happens, we can't communicate anymore with the mfi device.

OK, needs a specialist to answer. Could you use a DTS ? If you are approved MFI developer, you should have some support ?


Have you seen this thread ?

h ttps://forums.developer.apple.com/thread/91592

What Claude31 said but also…

our app was working great until ios 11.3

You should definitely file a bug about this; at a minimum it’s a binary compatibility regression.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

very strange as the problem occurs only with some accessories. Some works fine.

i've filled a bug, will hope i get an answer soon.

This is in production and clients are complaining a lot.

Thanks

Mat

This is in production and clients are complaining a lot.

In that case you should definitely open a tech support incident as well. It’s hard to say whether this should be a DTS TSI or an MFI one. It’s probably easiest to start with a DTS one, so that’s what I’m going to recommend. You can start here.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"
Ios 11.3.1 Creating a EASession with a connected accessory return nil
 
 
Q