Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Android] Value inconsistency when not using "Debug in Chrome"

See original GitHub issue

I am currently developing an app for iOS/Android. iOS does not have this issue. However, on my Nexus 6P, When converting strings such as this:

‘Fri Jul 24 2015 08:00:00 GMT+0900 (JST)’

into Date objects with var foo = new Date(), it seems valid when I have the Chrome Debugger on, yet when I turn it off, it becomes ‘Invalid Date’ in the Android Studio console, and the app cannot progress as it can’t convert it to a Date object.

I’m not sure which level of the stack this issue could be happening in, so addressing it here.

Issue Analytics

State:
Created 7 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

Naoto-Idacommented, May 10, 2016

FYI, when not using the debugger (I’m presuming it uses JSC?), it doesn’t like any datetime strings that contain anything related to timezones. Also, it doesn’t think dates separated by - are valid.

So I had to convert all my datetimes to “yyyy/MM/dd HH:mm:s” format for it to be convertible into a Date object when in debug/non-debug mode. Although, it lacks any timezone specs now.

0reactions

alexsmartenscommented, Apr 23, 2018

Hi there, I’m also having this problem