ios 8 crash related to UIPopoverPresentationController on ipad

I am trying to track down and debug an issue that is quite odd. My Ti app is built with: Ti SDK 3.4.1, XCode 6.1 ios 8.1.

Via the dashboard I see a user has experienced a crash in an ipad mini running ios 8.3. I have not yet been able to duplicate the exception, but I'm also trying to narrow down what the culprit might be.

The crash details are:

NSGenericException
UIPopoverPresentationController (<UIPopoverPresentationController: 0x172dcc00>) should have a non-nil sourceView or barButtonItem set before the presentation occurs.
 
0   
CoreFoundation 0x2c4745f7 __exceptionPreprocess + 127
1   
libobjc.A.dylib 0x39ffec77 objc_exception_throw + 36
2   
UIKit 0x2ffb84d5 -[UIPopoverPresentationController presentationTransitionWillBegin] + 2694
3   
UIKit 0x2fbe5fb5 __71-[UIPresentationController _initViewHierarchyForPresentationSuperview:]_block_invoke + 1194
4   
UIKit 0x2fbe4c97 __56-[UIPresentationController runTransitionForCurrentState]_block_invoke + 148
5   
UIKit 0x2f992a21 _applyBlockToCFArrayCopiedToStack + 306
6   
UIKit 0x2f90e71f _afterCACommitHandler + 456
7   
CoreFoundation 0x2c43b015 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 18
8   
CoreFoundation 0x2c4386f9 __CFRunLoopDoObservers + 274
9   
CoreFoundation 0x2c438afb __CFRunLoopRun + 912
10  
CoreFoundation 0x2c385b31 CFRunLoopRunSpecific + 474
11  
CoreFoundation 0x2c385943 CFRunLoopRunInMode + 104
12  
GraphicsServices 0x3373a051 GSEventRunModal + 134
13  
UIKit 0x2f977f21 UIApplicationMain + 1438
14  
[MY APP NAME] 0x0009fd63 0x00098000 + 32099
15  
libdyld.dylib 0x3a59aaaf start + 0

I do NOT explicitly use a PopOver anywhere in my application. That is to say, I never instantiate a titanium object from the namespace Titanium.UI.iPad.Popover. Is there some other Ti namespace that uses a UIPopoverPresentationController behind the scenes that I need to be aware of?

I will update with sample code if I am able to duplicate. For now just wondering if anyone has experienced this same exception while not explicitly using a popover??

Has anyone else out there experienced this issue?