3 ms·
I landed in Australia this morning and as soon as my phone updated to Dec 2 on the new network my phone started locking up immediately. It would go to the loadi
by jonstjohn 9y ago
I landed in Australia this morning and as soon as my phone updated to Dec 2 on the new network my phone started locking up immediately. It would go to the loading screen (spinner in middle of screen) every 8-12 seconds then reset to lock screen after 4-5 more, making it nearly impossible to even access settings for more than a few seconds. I was able to disable local notifications for the apps that I know use them after 3 or 4 tries (required some quick navigation to get to the right screen before it locked up). I captured the logs on a number of occasions but and saw a few anomalies in the logs including this one:
iPhone kernel[0] <Notice>: 2404.102 memorystatus: killing_highwater_process pid 736 [SpringBoard] (highwater 16) - memorystatus_available_pages: 26834
Possibly SpringBoard consuming too much memory because of the bug?
Additional saw some of these, although not sure if they are a factor:
iPhone dasd(DuetActivitySchedulerDaemon)[107] <Notice>: com.apple.healthd.achievement-asset-manager:E60402:[
{name: NetworkQualityPolicy, policyWeight: 11.400, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: [{[wifiQuality]: Required:100.00, Observed:50.00},{[networkPathAvailability]: Required:1.00, Observed:1.00},]}}
- giovannibajo1 9y agoIt’s a calendar bug. Local notifications are/can be scheduled 30 days in advance, so on Dec 2nd they can be scheduled on Jan 1st. I saw crash logs on Twitter mentioning “month 13”, so it looks like there’s an off by one bug in that calendar handling code
- stesch 9y agoStupid mistakes by big companies helped me fight the imposter syndrome.
- deleted 9y ago[deleted]
- userbinator 9y agoThat makes it all the more unusual, because I have not heard of Apple devices having problems on Dec 2 before now; unless they're rewriting everything frequently, which may also explain a few of the other severe bugs they've produced recently... yet another argument for not replacing things entirely just because they're "old" --- software needs time to mature and stabilise, and have its bugs fixed. Something as simple as a date addition should've been perfected by now.