Fixed

Bug

Status Update

No update yet.

Description

ka...@gmail.com

created issue #1

Sep 2, 2022 10:12AM

Hi,

While running test to generate baseline profile (also other tests) on emulator (details below), I am getting following error on my work app.

Tests are working fine on another emulator with google services (Api 33). I am unable to download Android 12 non-google images on my system so not able to verify on other emulators for baseline profile.

Component used: Macrobenchmark - Baseline Profiles / Other startup tests

Version used: 1.2.0-alpha02

Emulator:

Pixel XL API 30
Android 11.0
arm64

Device:

Mac M1 Pro

Error:

IllegalStateException: Unable to recompile com.masked (Output(stdout=Failure: package com.masked could not be compiled
, stderr=))
at androidx.benchmark.macro.CompilationMode.resetAndCompile$benchmark_macro_release(CompilationMode.kt:99)
at androidx.benchmark.macro.CompilationMode.resetAndCompile$benchmark_macro_release$default(CompilationMode.kt:72)
at androidx.benchmark.macro.BaselineProfilesKt.collectBaselineProfile(BaselineProfiles.kt:74)
at androidx.benchmark.macro.junit4.BaselineProfileRule.collectBaselineProfile(BaselineProfileRule.kt:93)
at androidx.benchmark.macro.junit4.BaselineProfileRule.collectBaselineProfile$default(BaselineProfileRule.kt:88)
at com.masked.benchmark.BaselineProfileGenerator.startup(BaselineProfileGenerator.kt:18)

Do let me know if you need anything else.

Comments

cc...@google.com <cc...@google.com> #2Sep 2, 2022 07:46PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.

NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.

ka...@gmail.com <ka...@gmail.com> #3Sep 5, 2022 11:38AM

I sent you the google drive links to the bug report and attached some screenshots of the process.
Number 2 is network settings when physical sim is active and number 4 is network settings when esim is active and physical sim is present in sim tray but is not detected

cc...@google.com <cc...@google.com> #4Oct 28, 2022 11:33PM

Reassigned to ra...@google.com.

Hi, I'm having the same issue. I contacted Google Fi support and they gave me a manually switch Sims. It worked. To manually switch Sims
*#*#794824746#*#*
Not an ideal solution however it's a patch until they fix it.

ra...@google.com <ra...@google.com> #5Nov 14, 2022 10:39PM

Thanks for that code! Not ideal, but helpful!

wd...@gmail.com <wd...@gmail.com> #6Jan 9, 2023 11:23AM

Another way to switch is to, hit the plus button on mobile network, download Sim, it'll fail

Now turn on airplane and turn off airplane..

Message last modified on Jan 9, 2023 11:23AM

ra...@google.com <ra...@google.com> Jan 11, 2023 12:10AM

Status: Won't Fix (Not Reproducible)

af...@gmail.com <af...@gmail.com> #7Jan 22, 2023 01:46AM

What if the Sim you are connected to is the esim not the physical sim?

yu...@schimke.ee <yu...@schimke.ee> #8Apr 7, 2023 10:02AM

Same issue on my Pixel 2 XL after upgrading from Android 9 to 10. The workaround dialer code works.

Message last modified on Apr 7, 2023 10:08AM

yu...@schimke.ee <yu...@schimke.ee> #9Apr 7, 2023 10:09AM

I am facing this issue as well. I had to manually to remove the physical SIM and reinsert it to get it working.

cc...@google.com <cc...@google.com> #10May 10, 2023 10:53PM

Status: Assigned (reopened)

Same here. This is a real and easy to reproduce issue.

ma...@google.com <ma...@google.com> #11May 10, 2023 11:54PM

I have the exact same issue. The other work around would be to unlock bootloader and downgrade to 9 or see if one of the 10 betas doesn't have the bug. I am seriously considering downgrading.

af...@gmail.com <af...@gmail.com> #12May 12, 2023 03:27PM

Same issue, just brutal and embarrassing

ma...@google.com <ma...@google.com> #13May 12, 2023 03:54PM

One more anecdote. Possibly out of date since this experience happened on Beta 2 in the second week of May.

The (physical) sim swaps did not help me, no matter how many times or in what order.

The only thing that worked for me was the dialer code that was provided by Fi support.

pr...@google.com <pr...@google.com> #14May 12, 2023 05:29PM

Same issue. Must eject and reinsert ATT sim after switching to Fi eSIM

gi...@google.com <gi...@google.com> #15May 15, 2023 12:06PM

I've been trying different solutions. The only thing that works is to use the change sim code above. Google, you need to fix this.

Message last modified on May 15, 2023 12:06PM

ma...@google.com <ma...@google.com> #16May 18, 2023 07:33PM

Please share the gdrive link as mentioned in

comment #3

.

NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.

ma...@google.com <ma...@google.com> Jun 5, 2023 10:42PM

Accepted by ma...@google.com.

ma...@google.com <ma...@google.com> #17Jun 5, 2023 11:59PM

Marked as fixed.

Here are the links for the bug reports

https://drive.google.com/file/d/1a_3WWsJH8yDCL1YAB3NW05XfbfAuXFoG/view?usp=sharing

https://drive.google.com/file/d/1Ioljr_130s4x6bHA5He5ddxv_i2m9MDU/view?usp=sharing

be...@google.com <be...@google.com> #18Aug 30, 2023 09:49AM

Status: Assigned (reopened)

This issue is extremely frustrating. I am currently traveling internationally and try to swap between T Mobile physical SIM and Google Fi eSIMdepending on the location. Can't do this anymore unless I ask for one of my wife's earrings to pop the SIM card out. She's getting slightly annoyed now. Hopefully there will be a fix soon.

Message last modified on Aug 30, 2023 09:50AM

cc...@google.com <cc...@google.com> Sep 7, 2023 05:37PM

Reassigned to ra...@google.com.

ra...@google.com <ra...@google.com> Sep 7, 2023 05:43PM

Reassigned to an...@google.com.

rk...@google.com <rk...@google.com> Sep 7, 2023 07:47PM

Reassigned to bo...@google.com.

bo...@google.com <bo...@google.com> #19Sep 14, 2023 08:42PM

Same issue please fix asap

bo...@google.com <bo...@google.com> #20Sep 15, 2023 10:46PM

Marked as fixed.

Google please fix this. How can you release this version without testing this function? On the behalf of all international travelers using Pixel 2, 😠😡🤬

an...@google.com <an...@google.com> #21Sep 21, 2023 09:04PM

Same issue, this is very annoying. If I had known this was an issue I would have waited for fix before upgrading.

IssueTracker

Error running test on an emulator : Unable to recompile * (Output(stdout=Failure: package * could not be compiled , stderr=))

Status Update

Description

Error:

Comments

cc...@google.com <cc...@google.com> #2Sep 2, 2022 07:46PM

ka...@gmail.com <ka...@gmail.com> #3Sep 5, 2022 11:38AM

cc...@google.com <cc...@google.com> #4Oct 28, 2022 11:33PM

ra...@google.com <ra...@google.com> #5Nov 14, 2022 10:39PM

wd...@gmail.com <wd...@gmail.com> #6Jan 9, 2023 11:23AM

ra...@google.com <ra...@google.com> Jan 11, 2023 12:10AM

af...@gmail.com <af...@gmail.com> #7Jan 22, 2023 01:46AM

yu...@schimke.ee <yu...@schimke.ee> #8Apr 7, 2023 10:02AM

yu...@schimke.ee <yu...@schimke.ee> #9Apr 7, 2023 10:09AM

cc...@google.com <cc...@google.com> #10May 10, 2023 10:53PM

ma...@google.com <ma...@google.com> #11May 10, 2023 11:54PM

af...@gmail.com <af...@gmail.com> #12May 12, 2023 03:27PM

ma...@google.com <ma...@google.com> #13May 12, 2023 03:54PM

pr...@google.com <pr...@google.com> #14May 12, 2023 05:29PM

gi...@google.com <gi...@google.com> #15May 15, 2023 12:06PM

ma...@google.com <ma...@google.com> #16May 18, 2023 07:33PM

ma...@google.com <ma...@google.com> Jun 5, 2023 10:42PM

ma...@google.com <ma...@google.com> #17Jun 5, 2023 11:59PM

be...@google.com <be...@google.com> #18Aug 30, 2023 09:49AM

cc...@google.com <cc...@google.com> Sep 7, 2023 05:37PM

ra...@google.com <ra...@google.com> Sep 7, 2023 05:43PM

rk...@google.com <rk...@google.com> Sep 7, 2023 07:47PM

bo...@google.com <bo...@google.com> #19Sep 14, 2023 08:42PM

bo...@google.com <bo...@google.com> #20Sep 15, 2023 10:46PM

an...@google.com <an...@google.com> #21Sep 21, 2023 09:04PM

Issue 244619933

Description

Error:

Issue summary

Comments

cc...@google.com <cc...@google.com> #2Sep 2, 2022 07:46PM

ka...@gmail.com <ka...@gmail.com> #3Sep 5, 2022 11:38AM

cc...@google.com <cc...@google.com> #4Oct 28, 2022 11:33PM

ra...@google.com <ra...@google.com> #5Nov 14, 2022 10:39PM

wd...@gmail.com <wd...@gmail.com> #6Jan 9, 2023 11:23AM

ra...@google.com <ra...@google.com> Jan 11, 2023 12:10AM

af...@gmail.com <af...@gmail.com> #7Jan 22, 2023 01:46AM

yu...@schimke.ee <yu...@schimke.ee> #8Apr 7, 2023 10:02AM

yu...@schimke.ee <yu...@schimke.ee> #9Apr 7, 2023 10:09AM

cc...@google.com <cc...@google.com> #10May 10, 2023 10:53PM

ma...@google.com <ma...@google.com> #11May 10, 2023 11:54PM

af...@gmail.com <af...@gmail.com> #12May 12, 2023 03:27PM

ma...@google.com <ma...@google.com> #13May 12, 2023 03:54PM

pr...@google.com <pr...@google.com> #14May 12, 2023 05:29PM

gi...@google.com <gi...@google.com> #15May 15, 2023 12:06PM

ma...@google.com <ma...@google.com> #16May 18, 2023 07:33PM

ma...@google.com <ma...@google.com> Jun 5, 2023 10:42PM

ma...@google.com <ma...@google.com> #17Jun 5, 2023 11:59PM

be...@google.com <be...@google.com> #18Aug 30, 2023 09:49AM

cc...@google.com <cc...@google.com> Sep 7, 2023 05:37PM

ra...@google.com <ra...@google.com> Sep 7, 2023 05:43PM

rk...@google.com <rk...@google.com> Sep 7, 2023 07:47PM

bo...@google.com <bo...@google.com> #19Sep 14, 2023 08:42PM

bo...@google.com <bo...@google.com> #20Sep 15, 2023 10:46PM

an...@google.com <an...@google.com> #21Sep 21, 2023 09:04PM

Add comment

Issue metadata