Finding and fixing bugs is a constant struggle with any software. It has been a painstaking process of narrowing down exactly what and where the bug resides in code. With Ink Calendar I group crashes into a few different categories.
- File read/write
- Microsoft Graph
- Unspecified Error
- null References
Recently I was emailed by a user who mentioned OneNote was unstable until they turned off ink analysis. So in Ink Calendar version 2.0.7 there is a new toggle switch to disable ink analysis.
Turning off ink analysis should help with crashes. If you make this switch and it helps please let me know. The ink analysis is a Windows 10 API, so if there is an issue, I’ll collect what I hear from users and reach out to Microsoft.
Other than analysis issues file read/write issues are largely related to the Microsoft Graph which does the cloud syncing. I can improve the cloud service, but some things are beyond the scope of Ink Calendar.
Finally null reference errors almost all come from getting appointments from Windows 10. The Windows 10 appointments API has some issues with not getting fresh appointments. Also there maybe intermittent access issues resulting in null references. There is a helper in Ink Calendar which checks to see if Ink Calendar has access to the user’s calendars. Even though this check runs before attempting to get calendar data, the data can still return null.
If you are seeing consistent repeatable crashes with Ink Calendar I would like to hear from you so I can get to the bottom of the issue.
As always thank you for using Ink Calendar and please feel free to email me (support at inkcalendar dot com).