It definitely doesn’t on Android, you’re right there.
So is there any reason why it seems to have stopped working for iOS?
It definitely doesn’t on Android, you’re right there.
So is there any reason why it seems to have stopped working for iOS?
We changed how we deal with fonts to make things a bit more consistent between platforms. For instance, you don’t need the build.settings entries any more. I would re-read the updated Font guide:
https://docs.coronalabs.com/guide/system/customFont/index.html
Rob
I’m away from my machine right now, but I’m sure that when I noticed it was not displaying the fonts yesterday I used native.getFontNames() to try and find out if ios was using different names for the font now.
I printed out all fonts returned by that function and every single one of my custom files was missing from the list. When I manually update my plist to include “fonts provided by application” the fonts appear in the table returned by native.getFontNames().
There still doesn’t seem to be an answer to the root cause of this issue:
Why does buildSettingsToPlist.lua not seen to work any more? It’s not copying any of the build.settings fields to the plist, when it used to copy all of them. Do I need to change something in my build.settings file, or has it been disabled accidentally between daily builds?
me too,
i got these warning when i use corona enterprise 2728
Sep 30 02:17:45.817: App: WARNING: The font (Calibri) could not be found. Using system font instead.
Sep 30 02:17:45.831: App: WARNING: The font (Calibri) could not be found. Using system font instead.
Sep 30 02:17:45.833: App: WARNING: The font (Calibri) could not be found. Using system font instead.
Sep 30 02:17:46.056: App: WARNING: The font (Calibri) could not be found. Using system font instead.
Sep 30 02:17:46.297: App: WARNING: The font (Calibri) could not be found. Using system font instead.
and the font name inside the ttf file is “Calibri”
I have the same problem with corona enterprise. It works fine on android but on iOS the fonts aren’t loaded. here are the fonts:
AdobeArabic-Bold.otf
AdobeArabic-Regular.otf
internal name in code:
fontName = “AdobeArabic-Bold”
fontName = “AdobeArabic-Regular”
Hi, I have the same problem.
SourceHanCodeJP-Bold.otf and SourceHanCodeJP-Normal.otf.
There are no problems with previous version #2644.
Corona Enterprise does not using the build.settings file. The fonts have to be added as file in the project and then you have to update the plist yourself to include the UIAppFonts table yourself.
Rob
I see. But this problem does not occur until #2687. Why do you think it is so?
I’ve just updated from Enterprise build #2541 to #2719 and I’m suddenly getting the same thing for fonts which previously had worked. I had never manually put any font details into my plist file, even when they worked.
Rob you said “Corona Enterprise does not using the build.settings file.” Is that a recent change? My understanding is that the build.settings file did get used to populate some values in the plist. There is even a file in Enterprise called “buildSettingsToPlist.lua” which can be found at /CoronaEnterprise/Corona/mac/bin/buildSettingsToPlist.lua
I’m having some other issues too, most noticably one where if I start the game in landscape it acts as though it’s still in portrait (our game supports both orientations). This worked before, and if I start in portrait then rotate to landscape it works, but starting in LS does not. I’m now wondering if this is another issue where the plist does not have correct values?
The plist is definitely not being populated like it was before. I just looked inside an ipa file I built yesterday using #2541, and the plist has loads of things that I’ve only ever specified in build.settings:
icon file names url types CoronaViewSupportedInterfaceOrientations FacebookAppID Fonts provided by application Required background modes Initial interface orientation UILaunchImages
These are all things that are now missing since I updated Enterprise to #2719 this morning, and while I can add them manually I currently have 8 apps on the go, and would prefer not to have to do this manually if the build.settings file could carry on doing it.
Edit: I’ve now tried adding the missing fields manually, and the game is behaving as expected again. But I’m still unsure of why the plist isn’t being populated like it was previously.
Maybe it’s just on Android we don’t copy anything over.
Rob
It definitely doesn’t on Android, you’re right there.
So is there any reason why it seems to have stopped working for iOS?
We changed how we deal with fonts to make things a bit more consistent between platforms. For instance, you don’t need the build.settings entries any more. I would re-read the updated Font guide:
https://docs.coronalabs.com/guide/system/customFont/index.html
Rob
I’m away from my machine right now, but I’m sure that when I noticed it was not displaying the fonts yesterday I used native.getFontNames() to try and find out if ios was using different names for the font now.
I printed out all fonts returned by that function and every single one of my custom files was missing from the list. When I manually update my plist to include “fonts provided by application” the fonts appear in the table returned by native.getFontNames().
There still doesn’t seem to be an answer to the root cause of this issue:
Why does buildSettingsToPlist.lua not seen to work any more? It’s not copying any of the build.settings fields to the plist, when it used to copy all of them. Do I need to change something in my build.settings file, or has it been disabled accidentally between daily builds?
me too,
i got these warning when i use corona enterprise 2728
Sep 30 02:17:45.817: App: WARNING: The font (Calibri) could not be found. Using system font instead.
Sep 30 02:17:45.831: App: WARNING: The font (Calibri) could not be found. Using system font instead.
Sep 30 02:17:45.833: App: WARNING: The font (Calibri) could not be found. Using system font instead.
Sep 30 02:17:46.056: App: WARNING: The font (Calibri) could not be found. Using system font instead.
Sep 30 02:17:46.297: App: WARNING: The font (Calibri) could not be found. Using system font instead.
and the font name inside the ttf file is “Calibri”
Hi,
Has this been resolved?
When running on Android device, I can’t get my custom font to render and it doesn’t show up using native.getFontNames(). I’ve tried several different fonts.
I’m using the latest daily build 2016.2818.
Are you all doing Enterprise builds or SDK builds?
Rob
I can only answer for myself, and yes, I’m using Enterprise.
Hi,
Has this been resolved?
When running on Android device, I can’t get my custom font to render and it doesn’t show up using native.getFontNames(). I’ve tried several different fonts.
I’m using the latest daily build 2016.2818.
Are you all doing Enterprise builds or SDK builds?
Rob