Why is Position's timestamp property nullable?

[jjoelson]

Thanks for creating this great package!

I was wondering why the Position timestamp property is DateTime? instead of DateTime. I did a quick scan of the getPositionStream implementation for iOS and Android and it looks like CLLocation.timestamp and android.location.Location.getTime() are the sources and should always return a value.

I didn't dive into the other platform code because I'm only using iOS and Android. Can I can safely assume that timestamp will always be non-null on iOS and Android? Or are there scenarios where it will be null?

[TimHoogstrate]

Dear @jjoelson,

Thanks for your support. It looks like a great improvement. Therefore, I label this issue as an enhancement.

Kind regards,

[TimHoogstrate]

Dear @jjoelson,

In the changelog of version 2.0.1 it is stated that:

"Bug fix where a null reference exception occurs because the timestamp of the Position could be null when fetching a Placemark using the placemarkFromAddress or placemarkFromCoordinates methods."

So it seems to have a valid reason to be there.

Kind regards,

[TimHoogstrate]

Resolved by 1362