3 Replies Latest reply: Mar 2, 2013 7:04 AM by MrHoffman
LotusDome Level 1 Level 1 (0 points)

## 2.33GHz MBPC2D running OS X 10.6.8, iPhone 4S running iOS 6.1.2 ##

 

Greetings, folks!

 

As there is no iOS System Technologies Discussion Community (AFAICT), this seems the best place to start . . .

 

I am baffled as to why some application file types can be copied (i.e. backed up) just fine to my iPhone 4S, and yet other file types (.textClipping, .scpt, .webloc, aliases, etc.) result in errors (mostly Error Code: -39) and corrupted files. The files are going into folders created using apps like PhoneDisk, iExplorer, FileApp, DiskAid, etc., and are copied with said apps, as well as with ChronoSync syncs. FUSE for OS X doesn’t help either.

 

Given claims that the iOS file system is HFSX—supposedly the Apple file system used for all their mobile devices that is nearly identical to HFS+ except for being case-sensitive—why are the files not copying properly from my Mac to my iPhone? This condition exists regardless of whether or not the iPhone is jailbroken and regardless of where in the file hierarchy the files are placed.

 

Thoughts?

 

Thanks!!

  • 1. Re: OS X File Type Constraints in iOS 6?
    twtwtw Level 5 Level 5 (4,690 points)

    My best guess: file types are registered with LaunchServices by various applications and the system.  If there's nothing that uses a particular file type, nothing is registered, and launchservices won't know what to do with such files.  None of the file types you've mentioned are used on iOS.  They may not actually be corrupt; can you copy them back to a Mac OS machine and see if they're recognized again?

     

    If you're just using your iPhone to transfer files between machines, zip them first.  iOS understands zip files (I think) and won' worry that it doesn't know what to do with the files inside.

     

     

     

    need to learn to spell-check before I hit the submit button...

  • 2. Re: OS X File Type Constraints in iOS 6?
    LotusDome Level 1 Level 1 (0 points)

    twtwtw wrote:

     

    They may not actually be corrupt; can you copy them back to a Mac OS machine and see if they're recognized again?

     

    They were corrupted, with zero data in many cases. Often, but not always, iOS would list the file’s data properly, but would change it to zero bytes when I tried to open the file (on my iPhone) from my Mac’s Finder. ChronoSync gives detailed reports on the sync errors; as soon as they are copied, they cannot be verified.

     

    If you're just using your iPhone to transfer files between machines, zip them first.  iOS understands zip files (I think) and won't worry that it doesn't know what to do with the files inside.

     

    Thank you, I never thought of that! Yes, trading zips back and forth does preserve the data. Unfortunately it is not overly convenient, unless I work out a system that zips every file I copy over . . .

     

    My best guess: file types are registered with LaunchServices by various applications and the system.  If there's nothing that uses a particular file type, nothing is registered, and LaunchServices won't know what to do with such files.  None of the file types you've mentioned are used on iOS.

     

    Hmmm. Should I try and impose updates to the iPhone’s iOS LaunchServices? I’ve worked (successfully) with LaunchServices on the Mac in the past and it is a bit of a “can of worms.”

     

    ;-)

     

    Thanks so much for your prompt wisdom!

  • 3. Re: OS X File Type Constraints in iOS 6?
    MrHoffman Level 6 Level 6 (12,465 points)

    LotusDome wrote:

     

    As there is no iOS System Technologies Discussion Community (AFAICT), this seems the best place to start . . . 

     

    I don't know whether you're enrolled in the iOS developer program or not...

     

    Here is the Apple Developer forum - iOS core.  Access to the developer forums are restricted to developers currently enrolled in the iOS, OS X or related programs.  If you're working with iOS in this area, you should already be a member of the iOS program.

     

    If you're seeing file corruptions on non-jailbroken iOS devices using supported paths to load files onto the device, then please radar (Apple bug reporter) the problem with the detail and source code necessary to allow Apple to reproduce this.   You'll need to be in the developer program to access the bug reporter.

     

    I would not expect Apple would really want to allow random file formats to be present on IOS, particularly if there are no applications associated with the file formats, and particularly if there can be or are security risks associated with the file formats.  Some of the well-known file formats can be problematic.  But this is entirely a guess.

     

    If you have a corruption bug arising using supported access paths and interfaces, please radar it.  Or if it's with particular applications, please check with the folks that are maintaining the application you're using to store the files.  Or, well, zip it and operate with that.

     

    There are some file transfer applications around for iOS if you're not programming iOS yourself.