AnsweredAssumed Answered

FileMaker will crash on point releases after .9 and runtimes don't work

Question asked by nickorr on Sep 5, 2018
Latest reply on Sep 9, 2018 by nickorr

( If there's an award for the weirdest FileMaker bug I think this should get it. )


Product and version (e.g. FileMaker Pro 14.0.3)




OS and version


Mac OS 10.13.6




FileMaker Crashes when it's set to anything later than 17.0.9 ( ie 17.0.10 ), and FileMaker runtimes built with v17v2 that have their own version number in the info.plist greater than .9 will fail to locate their own runtime files.


How to replicate in FileMaker Pro


Find the FileMaker Application, and right click on it, and go to "Show Package Contents".  Open the Info.plist file and edit the "Bundle version" value.  Change it from 17.0.2 to "17.0.10" and save the file.  Open FileMaker Pro application and it will crash on startup.  An example of the error :


Process:               FileMaker Pro Advanced [67944]

Path:                  /Applications/FileMaker Pro 17 Advanced copy/FileMaker Pro Pro Advanced

Identifier:            com.filemaker.client.pro12

Version:               ???

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           FileMaker Pro Advanced [67944]

User ID:               501


Date/Time:             2018-09-06 16:42:54.193 +1000

OS Version:            Mac OS X 10.13.6 (17G65)

Report Version:        12

Anonymous UUID:        DA2700FE-9669-0DD1-7EA8-8DD5CC7C29B1


Time Awake Since Boot: 850000 seconds


System Integrity Protection: enabled


Crashed Thread:        0


Exception Type:        EXC_CRASH (Code Signature Invalid)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY


Termination Reason:    Namespace CODESIGNING, Code 0x1


kernel messages:


VM Regions Near 0 (cr2):


    __TEXT                 000000010845e000-000000010942f000 [ 15.8M] r-x/rwx SM=COW  t  []


Thread 0 Crashed:

0   ???                           0x000000010d81919c _dyld_start + 0


Thread 0 crashed with X86 Thread State (64-bit):

  rax: 0x0000000000000000  rbx: 0x0000000000000000  rcx: 0x0000000000000000  rdx: 0x0000000000000000

  rdi: 0x0000000000000000  rsi: 0x0000000000000000  rbp: 0x0000000000000000  rsp: 0x00007ffee77a1bc0

   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000

  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000

  rip: 0x000000010d81919c  rfl: 0x0000000000000200  cr2: 0x0000000000000000


Logical CPU:     0

Error Code:      0x00000000

Trap Number:     0


Binary Images:

       0x10845e000 -        0x10942eff7 +??? (0) <698058C2-65AA-38B0-B1F9-16D4F3D05148> (null)

       0x10d818000 -        0x10d862acf +??? (551.4) <8A72DE9C-A136-3506-AA02-4BA2B82DCAF3> (null)


External Modification Summary:

  Calls made by other processes targeting this process:

    task_for_pid: 0

    thread_create: 0

    thread_set_state: 0

  Calls made by this process:

    task_for_pid: 0

    thread_create: 0

    thread_set_state: 0

  Calls made by all processes on this machine:

    task_for_pid: 608021

    thread_create: 0

    thread_set_state: 0


VM Region Summary:

ReadOnly portion of Libraries: Total=27.6M resident=0K(0%) swapped_out_or_unallocated=27.6M(100%)

Writable regions: Total=257.2M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=257.2M(100%)


                                VIRTUAL   REGION

REGION TYPE                        SIZE    COUNT (non-coalesced)

===========                     =======  =======

STACK GUARD                          4K        2

Stack                            256.0M        3

__DATA                            3016K        5

__LINKEDIT                        11.5M        3

__TEXT                            16.1M        3

shared memory                        8K        3

===========                     =======  =======

TOTAL                            286.5M       13


How to replicate in a runtime


Build a runtime from a FileMaker file.  Edit the info.plist inside the application to set the Bundle version to "15.0.10" for example.  Save and close the info file.  Open the runtime application.




I located this issue with runtimes to begin with, because my runtime has different version numbers to FileMaker itself, in my case it was 16.0.10.  When I did that, the runtime doesn't crash, but will give you an error that it can't locate the primary runtime file.  When you ok that dialog, then it asks you to locate the file manually.  Once located the runtime works just fine.  But the behaviour persists on restarts of the application, so makes them frustrating for end users.


I was going to submit this as a runtime issue only, as that's a legitimate bug and it's reasonable to expect runtime builders to set their own version number.  But obviously runtimes are deprecated, so I'm not sure whether any bugs such as this would be looked at.  In my case I was also code signing the runtime and setting other things such as icons etc as would any FileMaker runtime application developer.


But I was curious what would happen if FileMaker ever released a v10 patch of the application, and if it would have any effect.  Oddly, it crashes the entire application.


I don't think this is critical issue, but something as basic as the version number should cause a crash, and shouldn't break runtimes.


( And obviously users shouldn't edit the info.plist in their copies of FileMaker Pro anyway ).