SharedPreferences.getString return value wrongly appended with 4 spaces, when string ends with a \n [322667991]

Bug

Status Update

No update yet.

Description

da...@googlemail.com

created issue #1

Jan 29, 2024 02:18AM

Hi, very simple, 9 years from now this bug has been reported several times, but never fixed. While it might seem a "cosmetic" bug, fixable with a trim(), instead it drives crazy any developer which hit it for the first time. It takes hours of smoke and regression tests failed, and lots of money and time lost, to finally realize it is a miserable bug in the Android API. After 9 years, me also, I humbly propose the precious developers at Google Android to finally fix it. Hot to reproduce - again very simple: Any version, any device, from 9 years to the latest API 34. Steps:

create any String, append a <NL> (\n), eg. String s="Hello world\n";
save it with SharedPreferences.Editor.putString(STR,s);
get it back in another String, eg. String s2=SharedPreferences.getString(STR,null);
execute basic System.out.println("["+s2+"]");
Expected result: [Hello world ]
Actual result: [Hello world ]
conclusion: the new String returned with 4 more spaces appended from nowhere after the <NL> (\n) Good luck...

Comments

da...@googlemail.com <da...@googlemail.com> #2Jan 29, 2024 02:32AM

We gave up upgrading to Room because we need to use FTS3/FTS4 virtual tables. Any plants to support it?

vi...@google.com <vi...@google.com> #3Jan 29, 2024 12:36PM

Assigned to vi...@google.com.

Florina Muntenescu (Android developer advocate at Google) told me that FTS support will definitely NOT be in Room 1.0 final. It is postponed to an indeterminate later version.

vi...@google.com <vi...@google.com> #4Feb 4, 2024 12:25PM

It is possible to work with virtual tables and fts4 while using Room v1. You just need to create and access it by yourself using sql queries. Not perfect but it works for me (just did it a few days ago).
Can't wait for this feature to be in Room

da...@googlemail.com <da...@googlemail.com> #5Feb 5, 2024 10:51AM

If your FTS tables are separate from the rest of your model it's a viable solution. Mine are fully integrated with my model (almost all queries have JOINs with virtual tables) so it's a no-go.

vi...@google.com <vi...@google.com> Feb 7, 2024 02:14PM

Status: New

da...@googlemail.com <da...@googlemail.com> #6Feb 8, 2024 06:13PM

any news?

Issue 322667991