Steve,

I see this is only the following method that is called many times but I guess that's no issue:

-(void)calendarView:(IGCalendarView *)calView weekChanged:(NSDate *)date

I've added some logging in the asyncAppointmentRequest and notice the two calls are done duplicate and that explains the no data displayed initially.

Here is the logging:

2015-12-14 17:37:08.631 Gensys[10110:299696] Start of async request

2015-12-14 17:37:08.632 Gensys[10110:299696] request.start == 2015-12-12 23:00:00 +0000

2015-12-14 17:37:08.632 Gensys[10110:299696] request.end == 2015-12-20 22:59:59 +0000

2015-12-14 17:37:08.632 Gensys[10110:299696] Month doesn't exist

NOW THE WEB SERVICE CALL IS DONE

2015-12-14 17:37:08.633 Gensys[10110:299696] Start of async request

2015-12-14 17:37:08.634 Gensys[10110:299696] request.start == 2015-12-19 23:00:00 +0000

2015-12-14 17:37:08.634 Gensys[10110:299696] request.end == 2015-12-27 22:59:59 +0000

2015-12-14 17:37:08.634 Gensys[10110:299696] Month exists

2015-12-14 17:37:08.663 Gensys[10110:299696] Start of async request

2015-12-14 17:37:08.664 Gensys[10110:299696] request.start == 2015-12-12 23:00:00 +0000

2015-12-14 17:37:08.664 Gensys[10110:299696] request.end == 2015-12-20 22:59:59 +0000

2015-12-14 17:37:08.664 Gensys[10110:299696] Month exists

2015-12-14 17:37:08.670 Gensys[10110:299696] Start of async request

2015-12-14 17:37:08.670 Gensys[10110:299696] request.start == 2015-12-19 23:00:00 +0000

2015-12-14 17:37:08.670 Gensys[10110:299696] request.end == 2015-12-27 22:59:59 +0000

2015-12-14 17:37:08.670 Gensys[10110:299696] Month exists

NOW THE DATA COMES BACK FROM THE WEB SERVICE

I can't put my finger on why the call is duplicate. When I scroll horizontally to other weeks I still don't see any data. I disabled most other code and still no fix.

Hey Daan, 

Yes, so if too many requests are occurring, the current request object you had, would no longer be valid, and thus you would run into the issue. So, yea that makes sense. 

Problem is, I don't see that happening. 

You should see 2 requests when a particular View loads. One for the current week/month/day and one for the next week/month/day. 

Then when you scroll, you should see one additional request, as the calendar always keeps 2 date ranges in scope. 

I've attached my sample. if you could run it, could you let me know if you see what i'm seeing or if your still seeing multiple requests. 

Thanks, 

-SteveZ

Thanks for the reply,

I have removed all the NSOperation code and it still works. The invalidate I still need to display the initial data in the week view. This is probably because of another bug I mentioned before: In the week view the asyncAppointmentRequest is called too many times.

Let me try to explain my theory:

The first asyncAppointmentRequest adds the current month to the months array but it is not the current week call. While this call is getting data from the web service the second  asyncAppointmentRequest is called with the correct week which is displayed. At this moment the web service call has not finished and the appointments array is empty. If you could fix the issue where the asyncAppointmentRequest is called too many times that would fix my issue and then I can remove the invalidate call from the request.

Hey Daan, 

Yea you don't want to call invalidate in the request. It's just going to trigger another request. 

I'm not entirely sure why that code isn't working for you. 

I did notice one thing thats a  bit extraneous, but probably isn't the culprit

You're using the code from he sample browser for creating a background thread: 
[[[NSOperationQueue alloc]init] addOperation:[NSBlockOperation blockOperationWithBlock:^(void)

Thats not necessary, we did that in the samples browser to simulate async behavior, but you don't need to do that.

Could you clarify the following?

The first time the method is called for a month, you never see the appointments, correct? However, after that month is stored, when you scroll that week/month out of view and back into view, the appointments do show? 

If thats the case, then its probably safe to assume something funky is happening in the network side of the snippet. That would also explain why your "workaround" would work, b/c when you call invalidate, the async request will happen again, but this time, you're using your cached appts code snippet, which is why it then appears. 

Perhaps the request object is nil when you're returning the appointments?

-SteveZ

I have found a fix but I don't think it's a nice one (calendar flickers a lot and horizontal scrolling through weeks is very buggy with this implemented)

Added a boolean forceRefresh to the class.

When monthExists is true in the code from my previous post I set the boolean to true right [request provideAppointments:appts]; with the following code:

if (appts.count == 0)
   forceRefresh = true;

When the month doesn't exist (the else statement in previous post) I add the following code right after the [request proviceAppointments:appts];

if (forceRefresh)
{
   [_calendar invalidate];
   forceRefresh = false;
}

Well.. The data does show up this way and that is important for now.

Hope to hear from you if this is the solution to go with or if there are other ways of implementing a better solution.