weird behavior with files

[adelevie]

weird behavior with files

[interstateone]

I've ran into this same issue and have been troubleshooting for a bit. I can't seem to write a failing test, but using some existing production objects that have files associated with them will cause this to happen. When fetched (curl or Parse::Query) a "name" field is returned. When the Parse::File is initiated, the parse_filename variable is lost/not set and subsequently it can't be saved. Strangely, if I monkey-patch an identical File init method when testing with the production objects it works... which also prevents me from seeing what may be happening inside. I'm not much of a Ruby dev so I don't have the insight to determine what would cause this.

Some details on the production objects: They've been uploaded with a filename using the iOS SDK (the iOS SDK allows creating a file without one). They also have a user pointer like above, however this didn't have an impact when trying to write a test.

[adelevie]

A friend of mine who sent me this problem originally found a simple workaround, which was to delete the file from the hash before making the request to Parse. Following the sample code I posted:

colleague.delete("photo")

Not the best, but I probably will not be able to fix this myself.

[ericcj]

this sounds like what i fixed on master in #74