{"id":4879,"date":"2022-08-24T23:02:52","date_gmt":"2022-08-24T17:32:52","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-java-lang-numberformatexception-for-input-string-2019-11-27\/"},"modified":"2022-08-24T23:02:52","modified_gmt":"2022-08-24T17:32:52","slug":"solved-java-lang-numberformatexception-for-input-string-2019-11-27","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-java-lang-numberformatexception-for-input-string-2019-11-27\/","title":{"rendered":"[Solved] java.lang.NumberFormatException: For input string: \u201c2019-11-27\u201d"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

LocalDate and ThreeTenABP<\/h2>\n
    String dateString = \"2019-11-27\";\n    LocalDate date = LocalDate.parse(dateString);\n    int epochDay = (int) date.toEpochDay();\n\n    System.out.println(epochDay);\n<\/code><\/pre>\n
This snippet outputs:<\/p>\n
\n
18227<\/p>\n<\/blockquote>\n
The documentation explains:<\/p>\n
\n
The Epoch Day count is a simple incrementing count of days where day 0
\n  is 1970-01-01 (ISO).<\/p>\n<\/blockquote>\n
So my suggestion is that this number is fine for feeding into your BarEntry<\/code> constructor.<\/p>\n
toEpochDay()<\/code> returns a long<\/code>. If your constructor doesn\u2019t accept a long<\/code>, convert to int<\/code>. In the code above I did a simple cast. The risk is that we will get a very wrong result in case of int<\/code> overflow for dates in the far future or the far past. I prefer to do a range check to avoid that:<\/p>\n
    long epochDayLong = date.toEpochDay();\n    if (epochDayLong < Integer.MIN_VALUE || epochDayLong > Integer.MAX_VALUE) {\n        throw new IllegalStateException(\"Date \" + date + \" is out of range\");\n    }\n    int epochDay = (int) epochDayLong;\n<\/code><\/pre>\n
The result is the same as before. This check is the same check that the Math.toIntExact<\/code> method I mentioned in a comment does (available from Android API level 24).<\/p>\n
\n
I had converted this value 18227<\/strong> to normal date and it gives date
\n  of this year 1970\/01\/01<\/strong> and in JSON it’s 2019-11-27<\/strong> why? and
\n  how should i correct it?<\/p>\n<\/blockquote>\n
Let me guess, you effectively did new Date(18227)<\/code>. My suggestion is that you avoid the Date<\/code> class completely and stick to java.time, the modern Java date and time API. Why you got 1970 is: 18227 is a count of days<\/em> since the epoch, and Date<\/code> counts milliseconds<\/em> (since 00:00 UTC on the epoch day). So you got 00:00:18.227 UTC on that day. We already have a LocalDate<\/code> in the above code, so just use that.<\/p>\n
    System.out.println(date);\n<\/code><\/pre>\n
\n
2019-11-27<\/p>\n<\/blockquote>\n
Should you need to convert the opposite way, it\u2019s easy when you know how:<\/p>\n
    LocalDate convertedBack = LocalDate.ofEpochDay(epochDay);\n<\/code><\/pre>\n
The result is a LocalDate<\/code> with the same value.<\/p>\n
Question: Doesn\u2019t java.time require Android API level 26?<\/h2>\n
java.time works nicely on both older and newer Android devices. It just requires at least Java 6<\/strong>.<\/p>\n