Crash on using NSDate() without a formatter for date ranges

[patchthecode]

Crash on using NSDate() without a formatter for date ranges

[patchthecode]

Acknowledged. Taking a look

[patchthecode]

2 things.

1. The calendar calls the boundary delegates to find out its date boundary. You are supplying NSDate() to the boundary. Every time NSDate() is called, you are supplying a different date.

Ex.

1st call = 2016-03-01 01:06:03 +0000
2nd call = 2016-03-01 01:07:03 +0000

Difference by a ~ second. Since you are changing the boundary, the calendar thinks you want the boundaries updated and the whole layout reloaded. Now while this is logical that the calendar thinks this, it's sort of dumb.

I will make the following fix -> The calendar will only assume that the developer wants to change the date when the difference in the date is greater than 1 day-unit.

2. That being said, the calendar should not have crashed. It crashed because after it assumed number 1 above, it deleted its internal date-data in preparation to generate the new one given by your NSDate() function. But it should have done this on the main thread instead of a background one.

The two fixes are done. Testing now. Expect a new code push in a few hrs. In the mean time continue to use the work around. After the fix you should be able to use it like you wanted to.

[patchthecode]

Updated to 2.1.1
Can you let me know if you are still having the issue?

[soundsmitten]

Yes, 2.1.1 fixes the issue.