Perhaps as a temporary work around, you can take the users to a layout with thie field on it instead of using show custom dialog. This may not be ideal, but at least it avoids the crashing.
Thank you for the post.
To attempt to replicate this, I created a new database file in FileMaker Pro 12.0v3 with two fields, a global text field titled "input" and a regular text field called "password."
I stored "password" in record 1 of the password field, and wrote a script using custom dialog to pass the input field as a variable to determine which account to log into (see screenshot below).
I am able to leave the keyboard open and tap "OK" without FileMaker Go 12 quitting. I tested both locally and hosted on FileMaker Server 12 Advanced.
Please let me know if I am missing a step to replicate.
are other custom dialogs working in order - or does just every c.d. crash the iOS? Are special fonts in use on the Mac-side?
there was a known issue under FMGo11 (an update solved it) that caused problems like this (and kept us away from FMGo since it took 8 weeks to release the patch..). But FMGo12 runs fine, no problem with custom dialogs here.