Was the database file open or closed when you tried to create the runtime? It should be closed, I believe.
Changing the permissions on the file to read-write, but that changes the permissions in the solution...
Usually, FileMaker files have to have write permission as you can't save data otherwise. If you do need the file to be read only, you can always change the file property back to read only after the runtime copy of the file has been created.
The database file was, as required, closed. The file that error message (see screenshot) is referring to is not in the database file but is in
/Applications/FileMaker Pro 12 Advanced/FMI Runtime Resources/Runtime.app
It's the Info.plist inside Runtime.app.
Under FM11, the permissions for that Info.plist were quite different. I don't know if I ever changed those in thepast, so I don't have a point of reference.
i've seen this before on previous versions when the user does not have admin rights to the computer.
Are you logged in as a admin user on this system?
No, I'm not running as an admin -- I'm running as a "standard" user. Yet, I don't recall seeing this with FM 11 (aqnd I don't get this with building FM11 runtimes), but perhaps I have just forgtten.
I promise it happens in FMPA11 if your not an Admin.
If you give yourself admin rights you'll quit seeing this error.
It may not happen on FMP11 on all OS but I do know on Lion it does happen. Your confusion may come in the sense that you may have been able to generate runtimes as a standard user on previous versions of OS X.