Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.7.0
Issue ID
ISXB-1007
Regression
No
Stack Overflow exception when using a custom Bluetooth controller with BLEGamepad library on esp32
How to reproduce:
1. Open the attached “IN-78554“ project
2. Open Input Debugger (Window → Analysis → Input Debugger)
3. Ensure the custom Bluetooth controller is powered on and connected to your computer
4. In the Input Debugger, observe if the custom Bluetooth controller is listed under devices
5. Select the custom Bluetooth controller from the list of devices
6. Observe the result
Expected result: Custom controller is connected without any errors
Actual result: A Stack Overflow exception is thrown
Reproducible with: 1.4.2 (2022.3.33f1), 1.7.0 (2022.3.33f1) (users)
Reproduced on: Windows 10 (users)
Not reproduced on: No other environment tested
Note: CQA could not reproduce the issue due to not having the necessary peripherals
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.