Hello,
First, thanks for the SR and the quick support so far, i'm still having issues with the fact asyncAppointmentRequest is not called in many of my cases. I'm trying to reproduce these issues in the samples project so I can send the code.
There are a few other things I wanted to point out, there will be more as soon as I got it reproduced in the samples browser:
Moderate: When I set the delegate to igCalendarAppointmentDatasourceProtocolAsync and add the dayChanged, weekChanged, monthChanged and yearChanged methods with logging I notice the weekChanged is being called many times while year and month (have not checked the day view yet)
2015-12-11 11:05:39.386 SamplesBrowser[346:38334] yearChanged
2015-12-11 11:05:41.905 SamplesBrowser[346:38334] monthChanged
2015-12-11 11:05:43.746 SamplesBrowser[346:38334] weekChanged
2015-12-11 11:05:43.750 SamplesBrowser[346:38334] weekChanged
2015-12-11 11:05:43.758 SamplesBrowser[346:38334] weekChanged
2015-12-11 11:05:43.760 SamplesBrowser[346:38334] weekChanged
2015-12-11 11:05:43.782 SamplesBrowser[346:38334] weekChanged
2015-12-11 11:05:43.786 SamplesBrowser[346:38334] weekChanged
2015-12-11 11:05:43.804 SamplesBrowser[346:38334] weekChanged
2015-12-11 11:05:43.811 SamplesBrowser[346:38334] weekChanged
Minor: When I start the Appt Datasource Async on an iPad with iOS 9.0.2 building with XCode 7.1.1 I get the following trace as soon as the calendar loads:
2015-12-11 10:44:16.806 SamplesBrowser[326:33845] *** -[__NSCFCalendar dateByAddingComponents:toDate:options:]: date cannot be nil
Future exception.
A few of these errors are going to be reported with this complaint, then further violations will simply be ignored.
Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):
(
0 CoreFoundation 0x000000018632e7bc <redacted> + 252
1 CoreFoundation 0x000000018632e644 <redacted> + 96
2 SamplesBrowser 0x000000010018b034 __57-[igCalendarAppointmentDatasourceProtocolAsync loadAppts]_block_invoke + 1176
3 Foundation 0x000000018730f82c <redacted> + 16
4 Foundation 0x00000001872626c0 <redacted> + 96
5 Foundation 0x0000000187252918 <redacted> + 604
6 Foundation 0x0000000187311c20 <redacted> + 224
7 libdispatch.dylib 0x0000000100a89d30 _dispatch_client_callout + 16
8 libdispatch.dylib 0x0000000100a967f0 _dispatch_queue_drain + 1036
9 libdispatch.dylib 0x0000000100a8da20 _dispatch_queue_invoke + 464
10 libdispatch.dylib 0x0000000100a98908 _dispatch_root_queue_drain + 760
11 libdispatch.dylib 0x0000000100a98600 _dispatch_worker_thread3 + 132
12 libsystem_pthread.dylib 0x000000019b6c9478 _pthread_wqthread + 1092
13 libsystem_pthread.dylib 0x000000019b6c9028 start_wqthread + 4
)
Steve,
I have stripped the code and commented most of the code in the UIViewController. Still 4 calls to asyncAppointmentRequest. Files are in the attachment.
Yes that's great!
Just a little note about the header file, I already replaced BaseDetailViewController with UIViewcontroller so there are no surprises in that base class.
Good night!
Ps: I have no idea what time it is where you guys are from. It's been 11 pm here and i'm going to bed :)
Hey Daan,
Ok cool, i'm going to spend tomorrow morning trying to reproduce the issue using the code you sent as a foundation. I'm hoping i'll be able to reproduce the issue and identify if its just something gong on in the application or if we just need to make a fix on our side, in which case I'll make the fix and get your a private build ASAP.
I'll keep you posted either way.
-SteveZ
Yes the sample is working. I have been debugging and debugging last couple of hours. I added two screenshots in the attachment, both are executed twice, the first twice and then after that the second twice. It's not the selectedIndex on the tabbarcontroller cause I already called the CalendarViewController as a simple presentviewcontroller on another button and it gives me something else but is still called four times.
There is also the CalendarViewController header and implementation files. I truly have no idea what's going wrong or what i'm doing different than in your example besides using AFNetworking to retrieve the data.
Just wanted to tell that the support so far has always been great at Infragistics :-)
Hmm..
So to be clear, my sample was working for you, right?
If so, that means we're at least seeing the same thing there. So the question is, whats different in your actual application versus my sample?
The only thing that should trigger another appointment request call, would be calling invalidate somewhere on the calendar?
Can you take a look at your code, and make sure you're not doing that somewhere else in your code?