[Resolved] Custom Fonts No Longer Working?

In summary:

  1. We built our APK with one of the builds between 804 and 879 and uploaded to: https://play.google.com/store/apps/details?id=com.timespacemagic.marbles

  2. We used the custom font Coolvetica: http://www.dafont.com/coolvetica.font

  3. If you download the game you’ll see that the font works. (If you bother, it’s in the end of round score screen.

  4. We downloaded build 894 recently to compile the exact same untouched code and assets from back then, but the same custom font is no longer working.

  5. I thought it’s a build bug, so I downgraded to Build 840 to compile the exact same code. But the custom font still does not work.

  6. Device used for testing in all above steps is a HTC Desire Z running CM7.

Anyone has any idea why this is happening? [import]uid: 108204 topic_id: 30958 reply_id: 330958[/import]

I would like to point out that the custom font works in the simulator, just not on my HTC. [import]uid: 108204 topic_id: 30958 reply_id: 123816[/import]

I can’t see custom font on Simulator but it works great on android device.
Chek that your font is in the same directory with main.lua file.
If your font file name is “myfont.ttf” then in your code you should use only the file name without the extension “myfont” [import]uid: 138389 topic_id: 30958 reply_id: 123819[/import]

Hi vova, yes it’s in the same folder. Like I said, it’s the exact same code, assets and directories as I compiled a month ago to release on Play store. Nothing was changed. The one from a month ago using the exact same build of Corona loads the font on my phone, but not now.

Custom fonts are the number problem we’ve always had, because it’s incredibly selective of what works. Because of that we’ve experimented with everything, down to downloading a font editor to change the font name within the file and convert between ttf and otf, because somehow one or the other doesn’t work. [import]uid: 108204 topic_id: 30958 reply_id: 123829[/import]

I don’t have time to create a main.lua with a line of text and some font.
If you want you can post your example with your font and I will run it to see if it works for me. [import]uid: 138389 topic_id: 30958 reply_id: 123853[/import]

If your code hasn’t changed and the font is the same then please file a cut down bug report with sample we can run that shows the issue. Telling us which build it last worked in and when you noticed it had stopped would also be very useful.

Peach :slight_smile: [import]uid: 52491 topic_id: 30958 reply_id: 123861[/import]

I’ve just located the problem.

  1. A month ago the code was compiled in our office.
  2. Since last week we’ve had building problems in office, constantly giving us [Build Error #5] with no console error message.
  3. We gave up and synced our files to our home computers for compiling.
  4. Dropbox deems capital ‘C’ to be identical to ‘c’ in file names and does not sync that. Therefore causing the problem. We seriously need to start using Git.

Thanks for the help.

In other news, we keep getting [Build Error #5] with no error message, only in our office. What could be causing this? [import]uid: 108204 topic_id: 30958 reply_id: 123928[/import]

I would like to point out that the custom font works in the simulator, just not on my HTC. [import]uid: 108204 topic_id: 30958 reply_id: 123816[/import]

I can’t see custom font on Simulator but it works great on android device.
Chek that your font is in the same directory with main.lua file.
If your font file name is “myfont.ttf” then in your code you should use only the file name without the extension “myfont” [import]uid: 138389 topic_id: 30958 reply_id: 123819[/import]

Hi vova, yes it’s in the same folder. Like I said, it’s the exact same code, assets and directories as I compiled a month ago to release on Play store. Nothing was changed. The one from a month ago using the exact same build of Corona loads the font on my phone, but not now.

Custom fonts are the number problem we’ve always had, because it’s incredibly selective of what works. Because of that we’ve experimented with everything, down to downloading a font editor to change the font name within the file and convert between ttf and otf, because somehow one or the other doesn’t work. [import]uid: 108204 topic_id: 30958 reply_id: 123829[/import]

Thanks for updating this - glad to hear it’s working for you now.

RE that particular build error, this thread may shed some light; http://developer.coronalabs.com/forum/2011/04/26/build-error-5-build-failed-check-console-window-errors - it suggests a few possible causes.

Peach :slight_smile: [import]uid: 52491 topic_id: 30958 reply_id: 124258[/import]

I don’t have time to create a main.lua with a line of text and some font.
If you want you can post your example with your font and I will run it to see if it works for me. [import]uid: 138389 topic_id: 30958 reply_id: 123853[/import]

If your code hasn’t changed and the font is the same then please file a cut down bug report with sample we can run that shows the issue. Telling us which build it last worked in and when you noticed it had stopped would also be very useful.

Peach :slight_smile: [import]uid: 52491 topic_id: 30958 reply_id: 123861[/import]

I’ve just located the problem.

  1. A month ago the code was compiled in our office.
  2. Since last week we’ve had building problems in office, constantly giving us [Build Error #5] with no console error message.
  3. We gave up and synced our files to our home computers for compiling.
  4. Dropbox deems capital ‘C’ to be identical to ‘c’ in file names and does not sync that. Therefore causing the problem. We seriously need to start using Git.

Thanks for the help.

In other news, we keep getting [Build Error #5] with no error message, only in our office. What could be causing this? [import]uid: 108204 topic_id: 30958 reply_id: 123928[/import]

Thanks for updating this - glad to hear it’s working for you now.

RE that particular build error, this thread may shed some light; http://developer.coronalabs.com/forum/2011/04/26/build-error-5-build-failed-check-console-window-errors - it suggests a few possible causes.

Peach :slight_smile: [import]uid: 52491 topic_id: 30958 reply_id: 124258[/import]