Hi Randy,
Just adding the custom font file in the Copy Files will work, but you might
see a long delay on app startup. This is because iOS looks for the
PostScript name of the font. The "Font Mapping File" box is needed for
providing a mapping of the font name to its actual PostScript name (as
Thank you, Panos. I hadn't seen that thread… but, another thought. Since I’ve
included a font for the first time, I’ve been looking at that as a possible
issue.
I included the font in the app using the Copy Files pane of the Settings. Is
there something I was supposed to reference in the
Hi Randy,
See this thread:
http://forums.livecode.com/viewtopic.php?f=49=153346#p153346
This ("perBinaryResults") does not sound like a name for a plist key.
Best,
Panos
--
On Fri, Apr 14, 2017 at 3:42 PM, Randy Hengst via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hi All,
>
>
Hi All,
I’ve just received an email from apple that indicated a plist problem:
”We are reaching out to you because we were unable to process your latest build
uploads due to bad binaries. Specifically, your plists had an empty
perBinaryResults key"
When I open the plist from the build, I don’t
