-
Notifications
You must be signed in to change notification settings - Fork 811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application got crashed at JTACMonthLayout due to nil value #1378
Comments
can you produce a sample app with the issue please? |
can you produce a sample app with the issue please? |
I am having a similar Issue with a crash in JTACMonthLayout.swift+168. The problem is only present on iOS 17 and the app always crashes in the first few seconds of execution suggesting an issue while loading the view, where the cachedConfiguration has not been set, but the view is already being laid out. So far I have not been able to reproduce the crash nor produce a sample app with the issue, but it affects roughly 25% of my app's users on iOS 17, so this is not just a rare edge case. Maybe this additional context as to when the crash occurs can help you diagnose the issue. I will continue to look for ways to fix this and keep you posted on any progress. |
Ok, it help a bit, but do you have any crash logs at all? Or is it crashing in the same location as the image above? 8.0.5 has a fix for that very crash |
We have been using 8.0.5 for a while now, the issue only came up with iOS 17. You can find a crash log here. Yes, as mentioned above it crashes in JTACMonthLayout.swift on Line 168. |
im just updating to the latest xcode today. |
@timfraedrich possible. @Swathiga-proj @NIRANJANPRASAD |
i still need some sort of sample code. These things are important:
etc etc If you make a bare minimum sample app that closely resembles your real app i can know. forget about designing it, just a base app will do. If you are unable to do this, then we'll have to spend time here with many questions (since i am unable to reproduce it) Since its happening for some of your users (on ios 17) and not all on ios 17, then I am interested to see what setup you have. |
@timfraedrich You are experiencing this crash because you data source is not set by the time by the time the following code is run: strictBoundaryRulesShouldApply = thereAreHeaders || delegate._cachedConfiguration.hasStrictBoundaries Your data source should have been set before that code is hit. But regardless, you code should not crash, therefore I have updated the code base to make the code safer. fix done here 6b1f96b |
Also, adding to the confusion, The errors mentioned here on this issue are 2 separate errors. |
(Required) Version Number:
8.0.3
Description
trictBoundaryRulesShouldApply = thereAreHeaders || delegate._cachedConfiguration.hasStrictBoundaries
line 168
Thread 1: Swift runtime failure: Unexpectedly found nil while implicitly unwrapping an Optional value
Steps To Reproduce
Expected Behavior
Additional Context
The text was updated successfully, but these errors were encountered: