Playing Audio exported from Container Field will crash FileMaker Go

Issue report by databuzz

Product

FileMaker Go

Version

13.0.4

Operating system version

iOS 7.1.2

Description of the issue

I have a solution running locally on iOS devices that allows users to download files to a local container field from a server hosted files. These files are then exported to the temporary folder on the device and set to open automatically so they start playing the audio or video.

After downloading an audio file (around 60mb in size) and listening to that at some stage the audio stops playing and this message appears:

"filename.fmp12" is damaged and cannot be opened. Use the desktop product's Recover command to recover this file.

Clicking OK dismisses the error. Another dialog box then appears:

Confirm. Communication with the host was interrupted. Do you want to try to reconnect?

As I wasn't connected to any hosted databases (after the file was downloaded the remote file was closed) I click No and the FileMaker Go database closes and returns to the FileMaker Go home screen. Opening the file then results in none of the navigation buttons working - see this issue for a description:

http://forums.filemaker.com/posts/eba77df82a

I have to restart the device or force quit FileMaker Go to get it working again.

Steps to reproduce the problem

Export a large audio file (mp3/mp4) stored in a container field on FileMaker Go and have it open automatically so it starts playing the audio. The audio will stop playing with this error message:

Error. "filename.fmp12" is damaged and cannot be opened. Use the desktop product's Recover command to recover this file.

Expected result

Audio continues to play until the end of the audio file

Actual result

Audio stops playing with this error:

Error. "filename.fmp12" is damaged and cannot be opened. Use the desktop product's Recover command to recover this file.

Exact text of any error message(s) that appear

Error. "filename.fmp12" is damaged and cannot be opened. Use the desktop product's Recover command to recover this file.

Configuration information

I can send you a file that you should be able to easily reproduce the error on.

Workaround

N/A