Author Topic: WCL_E_OBEX_FORBIDDEN and other faulty cases  (Read 2633 times)

Offline alexey_gusev

  • Newbie
  • *
  • Posts: 34
  • Karma: 0
WCL_E_OBEX_FORBIDDEN and other faulty cases
« on: July 07, 2010, 10:39:01 AM »
Hi,

I'm getting WCL_E_OBEX_FORBIDDEN error for some phones when I attempt to connect with OPP. I don't have an access to such phones (they belong to anonymous people on the street :) ), so I can't tell if it is the user who clicks Decline, or it is just timeout reached or whatever else.

Development documentation does NOT explain when this error code is sent (as most of OBEX errors as well, unfortunately), so my question is how can I diagnose what's the problem? It'd be extremely helpful to have it all documented.

Cheers,
Alex

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: WCL_E_OBEX_FORBIDDEN and other faulty cases
« Reply #1 on: July 07, 2010, 12:50:40 PM »
Hi,

There is no way to know why that error sent as each vendor and each model works different.

Offline alexey_gusev

  • Newbie
  • *
  • Posts: 34
  • Karma: 0
Re: WCL_E_OBEX_FORBIDDEN and other faulty cases
« Reply #2 on: July 07, 2010, 01:16:16 PM »
I more than agree, it depends on the vendor, but is there any difference in WCL code between user rejection and other possible causes?

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: WCL_E_OBEX_FORBIDDEN and other faulty cases
« Reply #3 on: July 07, 2010, 01:23:51 PM »
As WCL has no build-in "mind reader" then there is no difference as it is impossible to know what is happened on phone's/user's side. From bluetooth side disconnect looks the same as reject (on some phones) and if connection already established (as for OBEX errors) China's man left leg knows what phone sends back.
But here is one good news: your error mostly means that user rejected the file. Of course no warranty :)

Offline alexey_gusev

  • Newbie
  • *
  • Posts: 34
  • Karma: 0
Re: WCL_E_OBEX_FORBIDDEN and other faulty cases
« Reply #4 on: July 07, 2010, 01:43:02 PM »
that's exactly the point: "and if connection already established (as for OBEX errors)" - I get the error at connection stage (not OBEX connection yet)

so does that (OBEX error) mean that it has connected but then most probably was declined by the user or it was turned down without user interaction. this is crucial factor as I don't want to re-send anything it the user actually declined it in the first place.

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: WCL_E_OBEX_FORBIDDEN and other faulty cases
« Reply #5 on: July 07, 2010, 01:53:54 PM »
That is impossible. Connection is elready establshed and the error may appears on OpenObex or on PUT. Connect function will never return any OBEX error.

Usualy (I do repeat: usualy) that means "user rejects the message". Otherwise you should get WCL_E_TIMEOUT

Offline alexey_gusev

  • Newbie
  • *
  • Posts: 34
  • Karma: 0
Re: WCL_E_OBEX_FORBIDDEN and other faulty cases
« Reply #6 on: July 07, 2010, 02:04:33 PM »
ok, thanks for the info :)

 

Sitemap 1 2 3 4 5 6 7 8 9