Font upload problems

[tortoise738]

Hallo team,

I am having real problems getting fonts that I upload to register within the app. I have followed the instructions here:

https://helpx.adobe.com/digital-publishing-solution/help/cards-layouts.html

...but I can't get the fonts to register in my preview app when I assign them to card metadata.

I have rebuilt the app several times and reinstalled but no joy.

If anyone felt charitable enough to have a look at the code below and see where I have inevitably gone horribly wrong, I would be very grateful!

{

  "version": "1.0",

  "description": "Example font file.",

  "fonts": {

    "AkzidenzBold": {

      "fileName": "AkzidenzGrotesk-Bold.otf",

      "postScriptName": "AkzidenzGroteskBQ-Bold"

    },

  "AkzidenzBoldCondensed": {

      "fileName": "AkzidenzGrotesk-BoldCond.otf",

      "postScriptName": "AkzidenzGroteskBQ-BdCnd"

    },

  "AkzidenzBoldCondensedItalic": {

      "fileName": "AkzidenzGrotesk-BoldCondItalic.otf",

      "postScriptName": "AkzidenzGroteskBQ-BdCndIt"

    },

  "AkzidenzBoldItalic": {

      "fileName": "AkzidenzGrotesk-BoldItalic.otf",

      "postScriptName": "AkzidenzGroteskBQ-BoldItalic"

    },

  "AkzidenzCondensed": {

      "fileName": "AkzidenzGrotesk-Cond.otf",

      "postScriptName": "AkzidenzGroteskBQ-Cnd"

    },

  "AkzidenzCondensedItalic": {

      "fileName": "AkzidenzGrotesk-CondItalic.otf",

      "postScriptName": "AkzidenzGroteskBQ-CndIt"

    },

  "AkzidenzCondensedItalic": {

      "fileName": "AkzidenzGrotesk-CondItalic.otf",

      "postScriptName": "AkzidenzGroteskBQ-CndIt"

    },

  "AkzidenzItalic": {

      "fileName": "AkzidenzGrotesk-Italic.otf",

      "postScriptName": "AkzidenzGroteskBQ-Italic"

    },

  "AmplitudeBlack": {

      "fileName": "Font Bureau - Amplitude-Black.otf",

      "postScriptName": "Amplitude-Black"

    },

  "AmplitudeBold": {

      "fileName": "Font Bureau - Amplitude-Bold.otf",

      "postScriptName": "Amplitude-Bold"

    },

  "AmplitudeRegular": {

      "fileName": "Font Bureau - Amplitude-Regular.otf",

      "postScriptName": "Amplitude-Regular"

    },

  "RockwellRegular": {

      "fileName": "ROCK.TTF",

      "postScriptName": "Rockwell"

    },

  "RockwellBold": {

      "fileName": "ROCKB.TTF",

      "postScriptName": "Rockwell Bold"

    },

  "RockwellBoldItalic": {

      "fileName": "ROCKBI.TTF",

      "postScriptName": "Rockwell Bold Italic"

    },

  "RockwellItalic": {

      "fileName": "ROCKI.TTF",

      "postScriptName": "Rockwell Italic"

    },

   "StoneSerifRegular": {

      "fileName": "StoneSerifStd-Medium.otf",

      "postScriptName": "StoneSerifStd-Medium"

    },

  "StoneSerifBold": {

      "fileName": "StoneSerifStd-Bold.otf",

      "postScriptName": "StoneSerifStd-Bold"

    },

    "StoneSerifBoldItalic": {

      "fileName": "StoneSerifStd-BoldItalic.otf",

      "postScriptName": "StoneSerifStd-BoldItalic"

    },

    "StoneSerifRegularItalic": {

      "fileName": "StoneSerifStd-MediumItalic.otf",

      "postScriptName": "StoneSerifStd-MediumItalic"

    }

  }

}

[brobeldesign]

Having the same problem here. We were able to get our fonts loaded into an app we've built. But, once we made a change to the app and re-signed the app, the fonts are no longer active. Wondering if there isn't something happening on the backend that's causing this.

Any assistance would be greatly appreciated.

[andreig1004688]

Hi,

We are looking into possible back-end issues that may be causing this.

Meanwhile, I just want to make sure that the .zip you upload has fonts and manifest right at the root of the .zip, and not within a folder in the .zip package. That is sometimes the "culprit".

Andrei

[brobeldesign]

Hey Andrei,

I can confirm that the zip has fonts and manifest at the root. They aren't contained within a folder.

[tortoise738]

Thanks Andrei - yes, I can confirm we have the fonts and manifest at root - no extra unwanted folders. For what it's worth, I am running this off a PC, and so that's where I did my zipping (although I did try rebuilding the app on a mac as well, no joy there either).

[andreig1004688]

Hi guys,

I've tried it myself with an iOS app, and worked for me.

Can you tell me what platforms are you trying this on? (iOS, Android, Win?)

Do you see the content you published in the app ? If yes, metadata are rendered with the default platform font, correct?

Are the font strings defined in the manifest an exact match with the strings you added to the card templates?

Regards,

Andrei

[brobeldesign]

Hey Andrei,

We've been building on iOS. And to answer your questions...yes, we are able to see the content published in the app and all metadata is currently in the default font. We've matched font names exactly. We have an earlier version of the app with the fonts working perfectly. We had to go back in and change a few icons and splashscreens, so we had to resubmit the app. Once we did that, the fonts stopped showing up.

[Neil_Enns_-_Ado]

Does it work if you build a new app instead of editing the existing one?

Neil

[brobeldesign]

Hey Neil,

Just built a new app...fonts still don't work.

[Neil_Enns_-_Ado]

Can you please email your fonts.zip file to me? Neile@adobe.com<mailto:Neile@adobe.com>. Thanks!

Neil

[Neil_Enns_-_Ado]

Ok, that didn't work IT blocked the zip file. Can you post it to Creative Cloud/Dropbox/Onedrive and send me the link?

Neil

[Neil_Enns_-_Ado · Accepted solution]

Hi guys,

Andrei (who owns our cards and layouts feature) was able to reproduce this issue in-house with the zip file provided by Ian. We're not sure why, but I've asked the App Builder team to investigate.

Neil

[brobeldesign]

Hey Neil,

Any progress on this? We're really dead in the water without the ability to add custom fonts.

Thanks,

Ian

[Neil_Enns_-_Ado]

Hi Ian,

Yes, we found a bug in the iOS viewer that only occurred when certain fonts were used and fixed it, although I'm not sure if it went out with our deployment on Monday. I'm investigating.

Neil

[brobeldesign]

Thanks Neil.

[Neil_Enns_-_Ado]

Hi Ian,

The fix was deployed with our release on Monday. If you rebuild your app in App Builder as of yesterday you should have the fix.

Neil

[brobeldesign]

Hey Neil,

We're able to get all fonts loaded!!! That's the good news...the bad news is, the descenders on y's, g's, etc. are getting chopped off at the bottom!

Thoughts?

[Neil_Enns_-_Ado]

That’ll be something related to the margins in your card layout. If you have your margins set too tight there won’t be enough space left in the text area for the descenders.

Neil

[brobeldesign]

Makes sense, but I have my margins set to zero, so not sure why the descenders would be cutting off.

Any other thoughts?

[Colin_Fleming]

Your card design may cause the descender truncation.

If text is set to the bottom of the card, with 0 padding (Card Properties: Layout), 0 Bottom Margin and a small Leading value (Card Properties: Metadata Style) -- you could get truncated descenders.

But this depends on your card design.

[brobeldesign]

This issue is happening on more than one card. But, as an example, here are the settings for one of the cards it's happening on...

Text is set to Middle, with 0 padding all around in Card Layout, leading 1 and 20 bottom margin in Metadata Style. I have 2 metadata fields and the descenders of the second metadata field are getting cut off.

Any ideas as to what I should change?