Export fail & features crash the app

suddenly i always get the following error, when i want to export the otf:

»export result
No File was created. The Reson is unknown.No File was created. The Reson is unknown.No File was created. The Reson is unknown.No File was created. The Reson is unknown.No File was created. The Reson is unknown.No File was created. The Reson is unknown.«

AND:
when i want to apply any feature, glyphs always hangs up. everytime.
this is since today, and restarting all the machines did not help

no matter what i try, nothing helps.
· all the features seem to be ok, the test renders no error.
· same for compatible masters
· unchecking autohinting and/or remove overlaps
· choosing different locations to save to, …

everything without result. it seems to be a problem with the certain file, since an older version exports like a charm. how can I find the problem

PS: georg, is this an issue better be discussed via mail or is it OK for you to put here in the forum?

Hi,

What version do you have? Can you send me the .glyphs file?

hey georg,

it is Version 1.1.8 (287).

i’m sending you a mail

i finally found the problem:

in the features i got the calt with several non-automatic settings

sub a a’ by a.calt;
sub aacute a’ by a.calt;
sub x x’ by x.alt;
and so on

now after i took all settings out one by one, i found the second line
to be the black sheep (sub aacute a’ by a.calt;)
i don’t yet know if this would be a combination that could actually apear,
but i can see no problem with it’s coding itself.

and the applying of features in the editor works as well again now after
random samples …

glyphs seems to not tell errors in the features, when they are not
automatically generatet from time to time)?! could this be changed?

and perhaps also the error message after failed exporting which does
say everything a bunch of times in a row … very redundant :slight_smile:

thank you so much for your effort, georg!

holy cow!
now i really know the problem: i made an typographic ’ instead of an '
i could figure it out since i made the code bold here and now it’s
apparent.

i am a creature of typographic habit, shame on me


but still: some more clear error messages would be so marvellous :slight_smile:

I added some tests to prevent the accidentally input of the wrong characters to prevent this crash and improved the error message. Thanks for reporting this.

awesome! thank you