Known Issues

Renderer features that do not work on some versions of Android

Android prior to 4.2

Stroked underline text

Stroking of underlined or strikethrough text is broken in versions of Android prior to 4.2. AndroidSVG will not attempt to stroke underlines or strikethroughs when running on Android 4.1 or earlier.

Android 4.3

Clip paths

There is a bug in Android 4.3 that has the effect of breaking the <clipPath> feature when using renderToPicture(). Any SVG files that use a <clipPath> will not render correctly. See Android issue 58737. If you are using renderToCanvas(), you will not be affected.

Android 6.0

Clip paths (again)

The problem with clip paths is back again due to two regressions in Android 6.0. Any SVG files that use a <clipPath> will not render correctly. See Android issue 200128. Unfortunately, this time, this bug affects both renderToPicture() and renderToCanvas().

To avoid this issue, please upgrade to AndroidSVG 1.3, which has new improved handling of clip paths. The new code avoids the above-mentioned issue, but uses Android APIs that are only available on Android 4.4 (Kitkat) or later. Older devices will continue to use the legacy clip path code.

Android 5.0 to 8.1

Erratically spaced text

Font sizes that are not whole numbers can result in erratically spaced glyphs (characters) in your text. This issue affects all versions of Android from 5.0 (Lollipop) to 8.1 (Oreo), but is fixed in Android 9.0 (Pie). See Android issue 37042531.

To work around this issue, upgrade to AndroidSVG 1.4 and avoid font sizes that have a fractional component. Ie. Use "24", rather than "24.35". It doesn't seem to matter what the current scale or transform is. It is the declared font size that matters.