• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: OBEXFileTransferServices reporting current path wrongly?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OBEXFileTransferServices reporting current path wrongly?


  • Subject: Re: OBEXFileTransferServices reporting current path wrongly?
  • From: Bubba Giles <email@hidden>
  • Date: Sat, 5 Jan 2008 18:59:34 -0800

Hi Hugh,

As always with these types of problems (and most Bluetooth issues), please run

/Developer/Applications/Utilities/Bluetooth/Packet Logger.app

and recreate the bug, then send us the packet logger document. We'll be able to confirm if there is a bug in the phone or in our stack. thanks,

jason

On Jan 4, 2008, at 4:37 AM, Hugh Cole-Baker wrote:

Hi,
I have been tinkering with the OBEX FTP service recently using Objective-C and OBEXFileTransferServices, and been having some problems. I can establish an OBEX session with my mobile phone and create an OBEXFileTransferServices object OK, and I have succeded in listing the contents of the phone's filesystem, but have now run into a problem. The OBEXFileTransferServices object isn't reporting its current path correctly in some situations. When carrying out the following sequence of operations:


1. Change directory to the root directory
2. CD to a subdirectory of the root (e.g. "/Memory stick")
3. CD to a subdirectory of the current directory (e.g. "/Memory stick/music/")
4. CD to the parent of the current directory (e.g. "/Memory stick")
5. CD to another subdirectory of the current directory (e.g. "/ Memory stick/theme")


At this point, a call to currentPath will return, not "/Memory stick/ theme/" as I expected, but "/Memory sticktheme/". It is not just in my application that this occurs, but also in the Bluetooth File Exchange.app, which will report the path incorrectly after doing the same thing.

I am wondering if this is a bug in my phone's software (a Sony Ericsson K800i) which would not surprise me, a bug in my code (possible) or a bug in Apple's Bluetooth framework. If it is a bug in Apple's framework, does anyone know of it or if it is fixed in Leopard (I am using 10.4.11)? The bug may be triggered by spaces in the folder name, as my phone contains two folders in the root, one named "Phone memory" and one named "Memory stick".
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >OBEXFileTransferServices reporting current path wrongly? (From: Hugh Cole-Baker <email@hidden>)

  • Prev by Date: OBEXFileTransferServices reporting current path wrongly?
  • Next by Date: Re: OBEXFileTransferServices reporting current path wrongly?
  • Previous by thread: OBEXFileTransferServices reporting current path wrongly?
  • Next by thread: Re: OBEXFileTransferServices reporting current path wrongly?
  • Index(es):
    • Date
    • Thread