You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 5, 2020. It is now read-only.
What steps will reproduce the problem?
1. Change language of phone to German (a lot other languages might be possible,
important feature of the locale: the decimal separator has to be a ",")
2. Launch WifiScanner
3. Observe continous messages of WifiScanner dying
What is the expected output? What do you see instead?
The Action should come up, instead messages inform of dying App.
What version of the product are you using? On what operating system?
Android 4.3 on Nexus 4, compiled as provided with Android 4.2.2 and Funf v4.2
and gson v2.1
Please provide any additional information below.
See the log file attached with the dump information. The problem is caused due
to number-representation problems inside BasicPipeline.writeDate (line 142):
the German system-locale will print the number with a "," as decimal separator,
which when creating the SQLite INSERT string makes it believe to be a column
separator.
Original issue reported on code.google.com by [email protected] on 19 Sep 2013 at 7:32
I had a look into the code, storage/NameValueDatabaseHelper.java seems to be
responsible for the creation of the insert line, which is:
db.execSQL(String.format(Locale.US, "insert into %s (%s, %s, %s, %s) values
('%s', '%s', '%s', %f)", ... )
This is getting strange...
Hm, what's the status on this issue? I dont' see a new 0.4.x version. I'm about
to start developing an app based on funf on a German Nexus 4. Would be good to
know if I should better not do that since the WifiScanner is quite important..
In case anybody is still wondering, I simply tried it out now and didn't
experience any issues with Wifi-scans on a German Nexus 4. I don't know if it
depends on the device or if it has been fixed somehow.
Original issue reported on code.google.com by
[email protected]
on 19 Sep 2013 at 7:32Attachments:
The text was updated successfully, but these errors were encountered: