@jeffb6688 custom fonts and the asset catalogue are not loaded into memory by iOS in time for the app to display these in the launch screen storyboard.
This is why iOS prepares cached snapshots of the launch screen. The cached snapshots are used at launch, not the supporting assets.
The workaround for images is as I described in my answer (in response to question by OP).
The workaround for custom fonts is more complicated.
Regardless of where they are placed in the file system, custom fonts are not loaded into memory by iOS in time for the app to display these in a launch screen storyboard.
So the workaround... we must prepare static image files that contain the custom font as a part of (embedded into) that image, in a size and layout to suit each screen orientation, size and resolution.
It won't take long to realise that this can become a significantly time consuming exercise given the great number of possibilities for screen orientation, size and resolution.
We could complain about this but Apple makes it clear in their iOS Human Interface Guidelines that launch screen images are not intended to be traditional "splash screens".
In their words...
- Design a launch screen that’s nearly identical to the first screen of your app.
- Avoid including text on your launch screen.
- Downplay launch.
Yes, Apple still approves apps with traditional splash screens, however this is contrary to their iOS HIG.