I apologize for this post being a bit vague. I don't have all the info I'd hope to have in front of me at the moment... but, I figured I'll at least get the ball rolling.
Unity Version: The last 3.5.x build. (I think it's 3.5.7)
NGUI Version: Paid version. Actual version number unknown at the moment (don't have my build environment available to me at the moment). Grabbed the build that would have been available in early March
After finding NGUI a few months ago, development of the UI in my Android game has been a pleasure. I'm not doing anything very fancy (nothing more than some position/scale tweening, a couple clipped panels, pulldown menus and button pressing). The UI works perfectly on many devices (Galaxy S3, S2, S, Motorola Droid 3, 4, Incredible, Nexus 7 and several other old models).
However, an out-of-town friend just got a Galaxy S4 and attempted to run my game. Unity starts without issue; he can see my Main Menu screen. But, as soon as he attempts to interact with any NGUI element the game will crash back to the Android home screen. He's tried pressing buttons and entering text into the game's sole text input box. Attempting either, ends with the same crash results.
I've sent him an early prototype of a different game that does not use NGUI and it runs on his S4 without issue. i.e. touch inputs for the non-NGUI based game don't crash said game.
Again, I apologize for the lack of any further concrete details at the moment; I'm certainly making many assumptions that something in NGUI (or my incorrect integration of NGUI components) is causing this issue.
My question to the forum community is if anyone has encountered any application crash issues or if anyone knows of any oddities when running on a Galaxy S4 (or any other high resolution Android device). My mind is being pulled toward 'resolution issue' simply because I don't see this issue on any of my non-high resolution devices nor do I see the issue on my Nexus 7 (running the absolute latest Android build pushed out by Google)... so it seems like it shouldn't be a 'cutting edge O/S' issue. I suppose it could be a Samsung TouchWiz issue, but, then again, I don't have any problems running on older TouchWiz devices (S3, S2, etc.)
Additioanlly, I, unfortunately, won't actaully be able to get physical access to an S4 to do any hands on debugging. Does anyone have any tips or 'best practices' of how I might be able to best troubleshoot/collect data from the device short of manually adding a ton of deug prints to a file that my friend can then email me?
