# Touch input broken on Android

**URL:** <https://forums.fusetools.com/t/touch-input-broken-on-android/745>\
**Category:** Bug Reports\
**Created:** [October 13, 2015, 3:17pm UTC](https://forums.fusetools.com/t/touch-input-broken-on-android/745 "2015-10-13T15:17:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sean\_Inge\_Asbjornsen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/sean_inge_asbjornsen/32/578_2.png) [@Sean\_Inge\_Asbjornsen](https://forums.fusetools.com/u/Sean_Inge_Asbjornsen)\
**Post date:** [October 13, 2015, 3:17pm UTC](https://forums.fusetools.com/t/touch-input-broken-on-android/745/1 "2015-10-13T15:17:56Z")

</div>

I’m experiencing some errors with the pointerIndex of touch input on Android after upgrading to Fuse version 0.8.2/3

1. When I tap with one finger on the screen Pointer.Pressed is being called twice.

2. When I tap with two fingers on the screen Pointer.Pressed is being called twice for index 0 and once for index 1. Pointer.Released is being called twice(as expected) and most of the time the indexes are 0 and 1, but some times they are both index 1.

These problems are causing us not to be able to differentiate between touches.

---

<div class="post-metadata">

**Author:** ![Anders\_Lassen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/anders_lassen/32/522_2.png) [@Anders\_Lassen](https://forums.fusetools.com/u/Anders_Lassen)\
**Post date:** [October 13, 2015, 3:19pm UTC](https://forums.fusetools.com/t/touch-input-broken-on-android/745/2 "2015-10-13T15:19:25Z")

</div>

Thanks for reporting.

This issue is already on file, we are working on it 🙂

---

<div class="post-metadata">

**Author:** ![Vegard\_Strand\_Lende](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/vegard_strand_lende/32/349_2.png) [@Vegard\_Strand\_Lende](https://forums.fusetools.com/u/Vegard_Strand_Lende)\
**Post date:** [October 14, 2015, 2:32pm UTC](https://forums.fusetools.com/t/touch-input-broken-on-android/745/3 "2015-10-14T14:32:04Z")

</div>

This issue is fixed! Included in next release (tonight I believe)