Author Topic: Issue with the top of the screen with NGUI in iOS (64-bit?!)  (Read 2365 times)

JulioArkavis

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 2
    • View Profile
I've been trying to solve this mysterious issue but I've ran out of things to try.

In all of my iOS devices (multiple iPads, and iPhones) the 10%(approx) top of the screen is not receiving input correctly. it seems to be sending that input information to the bottom 10% of the screen. Tapping on the bottom 10% of the screen works normally and has expected. This mysteriously started happening for no apparent reason but was around the time I started doing 64-bit builds and might also have been around the time I did updates to the devices.

To be sure I downloaded the latest version from the Asset store TODAY and the same behaviour was still happening.

Is this a know issue? And if so, is there a fix for this?

I looked around but couldn't find anyone with any similar issue besides http://www.tasharen.com/forum/index.php?topic=2884.0 but this is very old.

Any help on this issue would be greatly appreciated.


Edit 1: Everything works as expected in the editor and on Android.

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Issue with the top of the screen with NGUI in iOS (64-bit?!)
« Reply #1 on: July 21, 2015, 12:00:02 PM »
Sounds like a Unity issue. Create a simple repro case for them to look at that just prints the touch position in Update. Don't use NGUI at all.
  1. void OnGUI ()
  2. {
  3.     if (Input.touchCount > 0)
  4.         GUILayout.Label(Input.GetTouch(0).position.ToString());
  5. }

JulioArkavis

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 2
    • View Profile
Re: Issue with the top of the screen with NGUI in iOS (64-bit?!)
« Reply #2 on: July 21, 2015, 09:21:53 PM »
Thanks for the answer, turns out we had our AdMob plugin outdated and that was messing everything up for some reason. Disabling it fixed the issue. Everything is back to normal now, Thanks a lot for the support.