Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.3.0b5
Issue ID
569086
Regression
No
Failed to receive dispatch signal. status=-11 on Kindle Fire
On Kindle Fire (first generation) the "Failed to receive dispatch signal. status=-11" error is constantly printed out in the log when the screen is touched. This is reproducible even with an empty project. The regression was introduced in Unity 4.1.3f3 and is still present in Unity 4.3.0b5.
Tested on:
Amazon Kindle Fire (blaze, first generation) with Android 2.3.4
Tested with:
Unity Version 4.1.3f3 (9174d583c97b)
Resolution:
This happens on many devices with buggy event queues. Affected devices with previous to Jelly Bean Android OS. It is not possible to get rid of this message without causing deadlock situation on various devices.
Unity 5 is no longer bound to the native activity. Applications still forcing a native activity may still experience this behavior.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment