Android Question unexpected Asian character in toast with Material font

[Dave O]

I'm using csBuilder to prefix toast messages with a Material-font icon (checkmark), using the Material font TTF file (so I can get the latest icons).

This worked fine until recently, when I noticed that my latest builds (using B4A 11.x) are replacing the checkmark with an Asian (?) character:

Android 12 is adding the app icon on the left, but both Android 11 and 12 are showing the strange character instead of the checkmark.

On Android 5, the checkmark appears normally using the same build.

I'm baffled. Any ideas?

 

[Mahares]

I'm baffled. Any ideas?

I think you have to use it with the BCTextengine library, not CSBuilder

bc.Show($"[Alignment=Left][TextSize=20]
    [color=0xFFD21111][MaterialIcons=0xE5CA/][b]  B4XTable Results[/b]   
    [/color][/TextSize][/Alignment]
    "$)

 

[Erel]

It is not related to B4A version.
Maybe Google has changed something and they aren't allowing custom fonts in toast messages. Please create a small project with the toast message and upload it.

 

[Dave O]

Good idea. Attached is a minimal project that shows a checkmark on Android 5 - 10, but shows a strange character on Android 11 and 12.

It bundles the latest Material font as a TTF file in /Files, although the same thing happens using the built-in typeface.MATERIALICONS.

 

[Dave O]

Even stranger, I seem to remember the icon appearing normally on my phone using Android 11, but only changing to the strange character once I rebuilt it using B4A 11.x and updated my phone to Android 12. But I'm not certain about that.

 

[Erel]

It looks like a new restriction in Android 12. I don't see it mentioned explicitly in Android docs but they did make many changes to the toast behavior: https://developer.android.com/about/versions/12/behavior-changes-12#toast-redesign

If you are showing the toast while your app is in the foreground then you can use BCToast instead.

 

[Dave O]

Thanks for confirming this.

I'm showing it from a service that backs up the file to the user's Google Drive, so the app has often been closed by then.

The checkmark was a slightly more glance-able way of seeing that everything worked, but not strictly necessary, so I'll remove it and leave the usual text.

Cheers!