Status Update
No update yet.
Comments
pl...@gmail.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 3
- Android Gradle Plugin 8.8.0-alpha03
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
su...@gmail.com
press crtl+f11 to fix the issue
bo...@google.com
please be more specific and provide screenshots if possible
pl...@gmail.com
#5 I don't understand your comment. The steps are really clear. If the emulated device has got an HW menu button, you shouldn't see the overflow button in the action bar. The bug says, instead, that even if you create an emulator with hw button, the overflow button is *always* used.
es...@google.com
ja...@google.com
ja...@google.com
I have reproduced the problem.
I think we do not have a state variable that indicates the presence of this hard key on the device.
Will need to add that state and the logic to act on it.
I think we do not have a state variable that indicates the presence of this hard key on the device.
Will need to add that state and the logic to act on it.
ja...@google.com
As noted in #13, this is the intended behavior for a (typically older) device with a Menu key when running new software.
On a related note, we are considering restricting emulated devices to device/version combinations that are actually supported. This would prevent trying to run a new device with an old code version that won't boot. It would also prohibit older devices from trying run with incompatible newer code.
What do you think of this restriction?
On a related note, we are considering restricting emulated devices to device/version combinations that are actually supported. This would prevent trying to run a new device with an old code version that won't boot. It would also prohibit older devices from trying run with incompatible newer code.
What do you think of this restriction?
Description
SDK tools version (available in the "About" section of the 'android' tool
UI): 22.3
Eclipse version: 3.8.1
ADT plug-in version: 22.3
Platform targeted by your project: 22.3
Version of the platform running in the emulator: Android 4.4
STEPS TO REPRODUCE:
1. Create an Android 4.4 ARM emulator using a device definition that has a MENU button (e.g., Nexus S)
2. Run an app in the emulator that has an overflow (e.g., Messaging)
EXPECTED RESULTS: no "..." affordance in the action bar
OBSERVED RESULTS: visible "..." affordance in the action bar