Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.1p1
Issue ID
1016641
Regression
No
[UI][Android] OnEndDrag() is not being called while dragging and leaving the Application
The ScrollRect stops working correctly when you are in the middle of dragging and decide to leave the application in Android
To reproduce:
1. Download attached project and open in Unity
2. Run logcat
3. Build and Run the project on an Android device
5. Start dragging on the ScrollRect
6. While still dragging, just call up the Google Assistant on the phone using another finger and holding the Home button, or instead of calling the Google Assistant just select the Home button and go to your Home Screen
7. Go back to the application and you'll see the ScrollView is not moved back to its regular position
Notes:
- Logcat and project are shared in the comments section
- On iOS devices everything is fine and ScrollView is moved back to its regular position when you came back to the application
- The issue is that the OnDragEnd event never gets called, which it should if you have actually stopped dragging on the screen or leave the application
Devices:
- Google Pixel 2, OS: 8.1.0, CPU: arm64-v8a, GPU: Adreno (TM) 540
- iPhone 7, iOS: 11.2.6, CPU: A10
Reproduced on Unity 2017.1.3p3, 2017.2.2p3, 2017.3.2f1, 2017.4.1f1, 2018.1.0b13 and 2018.2.0a8
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [iOS] "UnityBatchPlayerLoop()" causes a freeze in the iOS application when it is put to the background and brought back to the foreground
- "Perform Selected" of Shortcut Manager window does not perform the shortcut in some cases
- Crash on mono_get_hazardous_pointer when running Play Mode tests in a specific project
- [iOS] ‘확인’(Done) and '취소'(Cancel) text is displayed as '...' in the on-screen keyboard when the System preferred language is set to Korean
- [sw-unity-6-1] Shadergraph panning area size is constant regardless of the size or the zoom level
Resolution Note:
Low priority defect for the moment. This bug is unlikely to be fixed in the near future.