@dotMorten_esri I have been looking at some things, which I am not able to check directly in the API but did with the previous version of the External Accessory listener I used.
What I found is that when setup the way EAAccessoryStream is setup if you check:
_session.OutputStream.HasSpaceAvailable();
it return false and if you try and do a Write operation on the stream the errors I see the same error described above.
However, if I add
_session.OutputStream.Schedule(NSRunLoop.Current, NSRunLoopMode.Default);
Prior to calling
_session.OutputStream.Open();
Then I am getting a true for HasSpaceAvailable(); and not seeing an error in the debug console. I need to make some changes in my app though to truly test the correction with my old listener because of changes I made to use the API now it does not process that output completely. In doing the testing I copied the EAAccessoryStream but with a couple changes to see what was happening
public override void Write(byte[] buffer, int offset, int count)
{
if ( _session?.OutputStream == null ) return;
bool spaceAvailable = _session.OutputStream.HasSpaceAvailable();
Console.WriteLine($"Calling stream Write - HasSpaceAvailable = {spaceAvailable}");
_session.OutputStream.Write(buffer, offset, (uint)count);
}
public override bool CanWrite => _session.OutputStream != null && _session.OutputStream.HasSpaceAvailable();
At first I had implemented a dummy class inheriting from NSStreamDelegate and assigns as delegate, but during testing that did not seem needed, although can give some additional information
Thanks
-Joe
Thanks,
-Joe
