site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer:sender; bh=0jdhZ2hD3iyK8yPNcNpRT+1hip6NnHARk1ns771/CTg=; b=Km2ztCN5vAGMLz1qfPpKmOAfZ4zutVEPAcgDsfTm+ohullgCbjU94UNM1ccHnbRooZN+6xBPZXahYKuwWFhnC8+PoAH3rKSZ5za5V5RR64Oyuz3DJQXb5gRwUer/GiPpgPoJvMPnLy62gqRDTztsSY1c6hnqDk7STNorSNb5uXg= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer:sender; b=XrG313EU5yPv8JSy3RVZfWy+kWznQwkhF+FIBbtQ6rKahvhjKPhnSnW6eEgRN8rpHyr3OQHegn1nhCNAcumQKenYVkITmbPxyCGm707qFjRO7hvcbvN5Ugi42KbxdfmpPQt45Iqxhy+gkyL91AFCz+6gckdMvuSegNh9qTjVVoY= 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 (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com