Spinner's dropDownHorizontalOffset attribute has no effect [79477181]

Obsolete

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ty...@gmail.com

created issue #1

May 9, 2018 11:18PM

NOTE:
This issue is a copy of an existing issue (36996315), but has to be refiled. According to a Google developer at Google I/O 2018 the bug's status probably got 'lost' when switching bug trackers for Android. The bug is still relevant, hasn't been solved (even though it's marked as Obsolete).

ORIGINAL REPORT:
- Steps to reproduce the problem (including sample code if appropriate).

Create a simple layout with a spinner and set any value for the dropDownHorizontalOffset attribute

For example -

<Spinner
android:id="@+id/spinner"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_centerInParent="true"
android:dropDownHorizontalOffset="50dp"
android:prompt="@string/spinner_title"
android:spinnerMode="dropdown" />

- What happened.

The dropdown popup window is displayed normally without any horizontal offset.

- What you think the correct behavior should be.

The dropdown popup window should be applied the horizontal offset *before* displaying it.

A quick dive in the Spinner source code revealed that though the horizontal offset is being applied to the popup window in the Spinner's constructor, it is not being taken into consideration in the computeContentWidth() which is called before displaying the spinner. Thereby causing the popup window to not have the proper horizontal offset.

Don't forget to mention which version of Android you're using, and/or which
device the problem appears on (model and Android version).

Nexus 10 4.4.2

ADDITIONS:
As can be seen in the comments on the original issue, this issue still exists and is still relevant.

Comments

ku...@google.com <ku...@google.com> May 10, 2018 06:26AM

Assigned to ku...@google.com.

ku...@google.com <ku...@google.com> #2May 10, 2018 07:27AM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

ty...@gmail.com <ty...@gmail.com> #3May 17, 2018 02:46PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

deleted

Restricted

0 B

deleted

Restricted

0 B

ku...@google.com <ku...@google.com> #4May 21, 2018 01:35PM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

[Deleted User] <[Deleted User]> #5Feb 8, 2019 09:17AM

Hmm, I feel the crash might be something related to separate/secondary process.

I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.

ad...@google.com <ad...@google.com> Oct 10, 2019 08:25AM

Reassigned to am...@google.com.

am...@google.com <am...@google.com> #6Oct 17, 2019 09:47AM

Status: Won't Fix (Obsolete)

On the contrary, there was no separate process before, when crashes started.

In the new build (with the aforementioned changes) I can see SIGSEGV crash, but only one instead of dozens and it has a bit different backtrace:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
liblanguage_id_jni.so (offset 0x11e000)

backtrace:
  #00  pc 000000000003c7c0  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003b960  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003bb48  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003bafc  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000036c98  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000032714  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000031cac  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000057438  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/oat/arm64/base.odex (offset 0x57000)

ru...@gmail.com <ru...@gmail.com> #7Oct 30, 2019 12:55AM

FYI, ML Kit launched a new language ID SDK in the latest release, which uses a new language ID model. https://developers.google.com/ml-kit/release-notes#august_11_2021

Could you try the new SDK version(17.0.0) to check if you can still repro this native crash? Thanks!

na...@gmail.com <na...@gmail.com> #8Apr 21, 2022 07:07AM

Thank you, I'll try it and check.

cl...@gmail.com <cl...@gmail.com> #9Jan 24, 2024 05:53PM

Hello. I have similar experience.

I'm using mlkit-language 16.1.1
I didnot meet this error until using AGP 4.2
I can get this error since using AGP 7.0
This error raised on Release build only(minimized by R8)
This error raised without obfuscation.