Search Issue Tracker
Won't Fix
Won't Fix in 1.7.X
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
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.
Resolution Note (1.7.X):
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.