RuntimeException [Android] Font asset not found Fonts/telerikfont.ttf

Progress® Telerik® UI for Xamarin Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Declined

Last Updated: 18 Nov 2020 17:34 by Chris

Didi

Created on: 11 Jun 2020 07:58

Category: UI for Xamarin

Type: Bug Report

RuntimeException [Android] Font asset not found Fonts/telerikfont.ttf

Runtime exception: Java.Lang.RuntimeException: Font asset not found Fonts/telerikfont.ttf, when trying to access any page with controls that use telerikfont, like AutoCompleteView, TreeView, etc.

6 comments

Chris

Posted on: 18 Nov 2020 17:34

Just want to make a note for anyone still having this problem, make sure that the fonts directory is "Fonts", not "fonts". It's case-sensitive.

ADMIN

Didi

Posted on: 17 Jun 2020 09:13

Hello guys,

Thank you for your patience and understanding.

The development team researched the issue and here are more details from the research:

- We have investigated the apk and bin/obj folders of the crashing application. The reason for the observed crash is missing “assets” folder in the final packaged apk that is installed. For some unknown reasons sometimes the “assets” folder was not added to the apk.

Based on this finding the exception could be caused by an issue in:

- Android Build Tools
- Gradle
- Visual Studio

We have carefully reviewed all information provided about the crash and noticed that most of our clients reported this issue after updating the Visual Studio to 16.6.0, with version 15 the issue cannot be reproduced.

We have researched the third option (crash when updating the Visual Studio to 16.6.0) and we have found a similar issue reported to the Visual Studio: https://developercommunity.visualstudio.com/content/problem/1045818/after-update-vs-2019-xamarin-app-debug-throws-exce.html

From this comment: https://developercommunity.visualstudio.com/comments/1069675/view.html it seems that there is a fix on the way.

Note that I have changed the feedback item status to Declined, as this is not a bug on our side.

Workaround until Microsoft includes the fix: clean and rebuild the project.

Regards,
Didi
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.

Headygains

Posted on: 12 Jun 2020 16:23

Ran into this issue as well.

Rebuild Solution Did the trick for me.

ADMIN

Didi

Posted on: 12 Jun 2020 09:51

Hello guys,

I understand this issue affects your Android development process. I can assure you that the issue is escalated to the development team and they will research it further.

Yes, the issue could be reproduced in PrdViewer when Toolbar is used, also in the ListView when grouping is applied. The reason behind this is Telerik Icons are used for the pdftoolbar, an arrow for TreeView, Listview - expand/collapse indicator, also in the imageeditor toolbar.

I have reproduced the issue on my side only two times and it happens when autocompleteview control was used. After that, I rebuild the solution and from then I cannot reproduce the exception.

Please follow the feedback item, so you will receive an email notification when there is an update in the item's status or more information about the issue.

Regards,
Didi
Progress Telerik

Kori

Posted on: 11 Jun 2020 16:41

I can confirm that I am experiencing the error "[Android] Font asset not found Fonts/telerikfont.ttf" while viewing pages with Telerik ListViews. My current workaround is to rebuild the solution before each debug session every time I updated code in my project, but that slows down the android development process a lot.

Dan

Posted on: 11 Jun 2020 15:56

Happens to me when using the PDF Viewer. I can get it to go away by cleaning my solution each and every time I want to switch to a new emulator. I don't like doing that because it is slowing down my development time dramatically. I am also not sure how it would affect my app releases. The releases may still have the bug in them when we build for release.