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
)
Major issue: I am able to reproduce my issue not seeing appointments in the samples browser.
What I have done is added the code from igCalendarAppointmentDatasourceProtocolAsync to igCalendarNavigation so that I can have a good navigational test. All seemed okay and everything was visible but when I add the following line of code at the end of viewDidLoad the appointments are not displayed for that week (when I go to month and back to the same week I still get no appointments:
[_cal navigateToDate:[NSDate date] forType:IGCalendarViewDisplayTypeWeek];
The reason I add this line is that I want to have the calendar initially in week view on the iPad.
I added the class as an attachment :-)
Hey Daan,
Thanks for the sample.
The Calendar is actually working correctly. However, when the WeekView request the appointments, there aren't any appointments available yet.
Thats b/c in the sample, the appointments from the CSV are being loaded in a background thread.
So when the calendar asks for appointments for that specific point in time, there are no appointments available.
If you don't load the CSV in the background, then it works fine. Or you could call invalidate after the appointments are loaded and reloaded the calendar view.
Hope this helps,
-SteveZ
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.
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.
Thanks for the stripped down version.
I tried it out, and cleaned out all the commented code, but its still not happening for me.
I've attached the sample. Can you verify your'e seeing the same thing?
I see the sample and everything working fine there. The only other difference I see is that you are using a storyboard where as we're using seperate xib files for the user interface.
I'm running out of ideas and without the CalendarView source code there is no way I can debug the issue. As you saw I stripped the entire code and do a simple call to the UIViewController. Nothing special just like in your sample.
Therefore I also checked the project settings and made some changes there. Also no result.
Perhaps the projects are using different versions of the IG Framework?
Can you insert the following line of code, in both the sample application, and in your actual app?
NSLog(@"%@", [IGBuildVersion buildVersion]);
I just want to make sure that your application isn't holding on to an older version.
Ok, so its definitely using the same build.
Maybe you can try using Sync callback with your simplified sample, and see if thats getting called 4 times?
2015-12-16 08:38:09.239 Gensys[28167:1603930] 2015.2.103