null is not an object (evaluating 'date.split') about react-timestamp

[nathanhoad]

Would you be able to give me an actual value for correctTime that I can test against?

I've tested the component inside a ReactNative app and the only way I can get it to say null is not an object (evaluating 'date.split') is by giving it Number("some string") or Number(undefined) as the time prop.

[pzehle]

Test is with this value, which is the one I'm getting from the API, in milliseconds: 1483041600000. I need to convert it to seconds in order to work with this module, otherwise I'm getting a date of year 4100~. Thanks!

[nathanhoad]

I get '30 Dec 2016' when I use Number(1483041600) as the time prop.

What version of react-timestamp are you using?

[pzehle]

Yes, if I hard-code the value it works fine, just please try to divide the value I gave you by 1000 and then use that result as the time prop.

[nathanhoad]

When I use this code:

    render() {
        var correctTime = 1483041600000;
        correctTime = Math.floor(correctTime / 1000);

        return (
            <View style={styles.container}>
                <Text>Value: {correctTime}</Text>
                <Time time={Number(correctTime)} format="date" component={Text} />
            </View>
        );
    }

I get this on screen:

[pzehle]

I'm doing exactly the same, but I'm using it inside a renderRow() function of a ListView, could you try that please?

[nathanhoad]

Components generally have no knowledge of their parent but just to make sure I tried rendering a ListView:

    renderRow (post) {
        var correctTime = Number(post.publish_date);
        correctTime = Math.floor(correctTime / 1000);
        
        return (
            <View style={styles.cell}>
                <Text style={styles.title}>{post.title}</Text>
                <Text>Value: {correctTime}</Text>
                <Time time={Number(correctTime)} format="date" component={Text} />
            </View>
        )
    }

And got this:

[pzehle]

Ok. Well, I'm still getting the same error, so you can close this issue if you want, and I'm going to keep looking for a solution, if I find anything else I'll let you know. Thanks again for you support.

[nathanhoad]

Ok I'll close it for now but feel free to comment back here if you find out any more info.

[pzehle]

Ok, thanks.