I’m currently build testing, and I’m getting reports of touch not working. Every device that doesn’t work with touch is non-samsung so pixel devices and basically anything else.
I’m using the latest 2022.3.12, anyone else have this problem?
One person was able to get touch working by connecting a mouse.
According to this:
Unity Issue Tracker - [Android] Touch input is unresponsive when building for Pixel 7 Pro device (unity3d.com)
A similar issue was fixed in 1.6.2, but there’s still comments reporting the same issue as of late september.
Maybe the issue came back in 1.7.0?
We tried on a Pixel 6 and the touch position is returning negative values.
In short the center of the screen is (0,0) which based on documentation is not correct. This is not the behavior on my samsung device, it’s position aligns with screen resolution with bottom left being (0,0) and top right being the screen resolution.
So touch is working, but the positions are all wrong which is making the UI not work.
We found the cause, for some reason the PlayerInput component caused this problem. Removing it enabled touch on the non-samsung devices…
But, isn’t this needed for our other input stuff? It seems to be related to multiplayer stuff which we don’t need…hm…
I believe I have input set to both… maybe the fall back is working but input system is not?
Still having issues with this and trying to isolate the problem, not having a non-samsung phone doesn’t help
I have submitted a bug report with a build and scene with the issue.
I bought a pixel 6 and i simply can’t get touch working in it.
After working all night on this, I found the issue is the action asset, either it is corrupted or I dunno what.
But even copying the data from the default to my custom one didn’t work, but doing the reverse did work.
This could be a result of moving between unity versions.
Now touch doesn’t work with Samsung devices what the fuck is going on?
EDIT: NVM this was a config issue, I didn’t have auto switch enabled.