Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
3
Found in
2018.4
2019.3
2020.1.0a17
2020.1.0a23
2020.2
Issue ID
1241180
Regression
Yes
[iOS] MFI controller button inputs are not processed
Reproduction steps:
1. Open project in "project.zip"
2. Build for iOS
3. Connect a supported MFI controller to an iOS device (tested with Dualshock 4)
3. Deploy the project to the iOS device using Xcode (IMPORTANT: check note 1)
4. A square will appear in the center of the screen every time you press a button
5. Try pressing some buttons on the connected controller
Unexpected behaviour: button presses are not processed
Reproducible with: 2018.4.22f1, 2019.3.12f1, 2020.1.0a17 -> regression, 2020.2.0a9
Not reproducible with: 2017.4.40f1, 2020.1.0a16
Devices tested:
Reproducible with:
VLNQA00310 iPad Pro 12.9 (iOS 13.4.1),
Not reproducible with:
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540 (XboxOne controller)
AppleTV (tvOS 13.3.1)
Notes:
1. After application launches, Minimize and Maximize the application as there is an issue where the controller does not connect until the app is Minimized and Maximized 1211074
2. This issue has been backported into 2018.4, 2019.3 streams
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
- Resize to Fit option for Import Activity window's Columns does nothing
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b13.3955
Resolution Note (fix version 2019.4):
Fixed in 2019.4.1f1
Resolution Note (fix version 2018.4):
Fix has been verified in 2018.4.25f1 (b07bfa0a8827)