You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Xamarin.Azure.NotificationHubs.iOS package throws an error in iOS:
2023-03-02 15:55:24.309 *** -[NSCalendar isDate:equalToDate:toUnitGranularity:]: date1 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 0x0000000192d7b4c4 42CCFC7B-FF32-3D25-8F01-CCB2AD843A8B + 296132
1 0x000000010bac8d0c -[MSInstallation isEqualToMSInstallation:] + 332
2 0x000000010bac901c -[MSInstallation isEqual:] + 100
3 0x000000010bad7a8c -[MSDebounceInstallationManager execute] + 96
Another package from Microsoft had the same issue and it was fixed there...unfortunately that isn't the one we are using due to other issues it has.
The Xamarin.Azure.NotificationHubs.iOS package throws an error in iOS:
2023-03-02 15:55:24.309 *** -[NSCalendar isDate:equalToDate:toUnitGranularity:]: date1 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 0x0000000192d7b4c4 42CCFC7B-FF32-3D25-8F01-CCB2AD843A8B + 296132
1 0x000000010bac8d0c -[MSInstallation isEqualToMSInstallation:] + 332
2 0x000000010bac901c -[MSInstallation isEqual:] + 100
3 0x000000010bad7a8c -[MSDebounceInstallationManager execute] + 96
Another package from Microsoft had the same issue and it was fixed there...unfortunately that isn't the one we are using due to other issues it has.
See this bug in the other repo:
Azure/azure-notificationhubs-ios#112
And this fix:
Azure/azure-notificationhubs-ios@4f368bc
The text was updated successfully, but these errors were encountered: