Error 0x00050015

[mentosan]

Hi

I know this is a very special case, but I am trying my luck anyway

Got our client/server solution working, no issues whatsoever.
We also use our product internally deployed as an App-V package.
Very strangely when running virtualized I get 0x00050015 when trying to enumerate characteristics:

* the call below works well, I am able to list and find our custom service
client.ReadServices(wclGattOperationFlag.goReadFromDevice, out wclGattService[] services);
* the call below gives 0x00050015
client.ReadCharacteristics(service, wclGattOperationFlag.goReadFromDevice, out characteristics);

Any idea what could cause that 0x00050015 error in this case?  I suspect some wrong (restrictive) COM isolation model on our side when building the package. Do you use any COM calls internally?

Thank you,
Radu

[Mike Petrichenko]

Hi,


Unfortunately this error indicates that something wrong but driver does not provide any additional information about the error.

Try to change goReadFromDevice to goNone.

Yes, there are lot of COM calls because all WinRT API is actually COM based API. But there should no be any COM issues cause Bluetooth Framework does all preparation internally.

[mentosan]

OK, it is what I was afraid of. There are several COM isolation modes available for App-V, most probably I've chosen a wrong one.
We have problems using the Windows Location Services too, and I saw in their code, they also use COM.

Thank you very much, at least I know in which direction to search -> COM.

[Mike Petrichenko]

Probably yes, that can be a problem.

[mentosan]

If you mentioned the goNone, could you please elaborate on the difference between goReadFromDevice and goNone. TBH from the docs I didn't fully understand and thought goReadFromDevice is always 'safe' and delivers fresh data

[Mike Petrichenko]

There are 3 options:

goNone - uses default drivers settings (driver decide what is better), also should be used if device is "not connectable";
goReadFromCache - cache value and returns it without asking device for value;
goReadFromDevice - always ask device for current value.