Experimental annotation from a different artifact not generated correctly with udpateApi [159033688]

Fixed

Bug

Status Update

No update yet.

Description

xi...@google.com

created issue #1

Jun 15, 2020 05:39PM

When marking an API as experimental in artifact A, if the annotation is from another artifact B, the updateApi in artifact A does not generate the correct result.

checkApi fails and ask for version increment even if the new API is experimental.

When calling updateApi with -PForce, the experimental API is added to current.txt, and the experimental annotation is missing.

CL with the issue. aosp/1312020

Comments

al...@google.com <al...@google.com> #2Jun 15, 2020 06:28PM

Reassigned to me...@google.com.

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?

au...@google.com <au...@google.com> #3Jun 15, 2020 09:29PM

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

ap...@google.com <ap...@google.com> #4Jul 6, 2020 05:02PM

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.

au...@google.com <au...@google.com> Aug 12, 2020 04:20PM

Marked as fixed.

ap...@google.com <ap...@google.com> #5Apr 28, 2021 05:33AM

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.

Issue 159033688