Re: Occasional NPEs from ERXTimeZoneDetector
Re: Occasional NPEs from ERXTimeZoneDetector
- Subject: Re: Occasional NPEs from ERXTimeZoneDetector
- From: Paul Hoadley <email@hidden>
- Date: Thu, 23 Jun 2016 19:25:52 +0930
Hi Ramsey,
On 20 Apr 2016, at 2:24 AM, Ramsey Gurley <email@hidden> wrote:
> That’s probably something that doesn’t live in your zones array, so zonesWithRawOffset is returning an empty array of which lastObject returns null, and thus the null pointer exception. Without knowing the zone string causing the problem, it’s a tough one. I’d probably start by logging that on a NullPointerException and trying to handle that event properly. You could go into handleException on the app and log the ERXSession.session().objectStore().valueForKey(“detectedTimeZone”) on any NPE perhaps.
detectedTimeZone is consistently “180,1,0”. It’s the DST parameter that’s causing the problem. zonesWithRawOffset(180, true, false) returns null, but zonesWithRawOffset(180, false, false) returns an array of 27 zones.
Any thoughts?
--
Paul Hoadley
http://logicsquad.net/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden