Pie API 28 emulator image has severe problems [348683477]

In Progress

Bug

Reviewed (L1)

Status Update

No update yet.

Description

ub...@gmail.com

created issue #1

Jun 22, 2024 06:21PM

Please Read: https://developer.android.com/studio/report-bugs.html#emulator-bugs

Android Studio Version: Android Studio Koala | 2024.1.1
Build #AI-241.15989.150.2411.11948838, built on June 10, 2024
Runtime version: 17.0.10+0-17.0.10b1087.21-11609105 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.5
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 10
Metal Rendering is ON
Registry:
  ide.instant.shutdown=false
  ide.images.show.chessboard=true
Non-Bundled Plugins:
  com.developerphil.adbidea (1.6.15)


Emulator Version (Emulator--> Extended Controls--> Emulator Version): 35.1.8-11793064
Hypervisor Version: HVF 14.5.0

Android SDK Tools: 26.1.1

Host Operating System: macOS 14.5

CPU Manufacturer: Apple CPU
Virtualization is supported

Bare metal
64-bit CPU

RAM: 16384 MB

GPU: 

Build Fingerprint: Android/sdk_gphone_arm64/generic_arm64:9/PSR1.210301.009.B6/9767327:userdebug/dev-keys

AVD Details: Name: Small_API_28
CPU/ABI: arm64
Path: /Users/uli/.android/avd/Pixel_3_API_28.avd
Target: google_apis [Google APIs] (API level 28)
Skin: 720x1280
SD Card: 100M
AvdId: Small_API_28
PlayStore.enabled: false
avd.ini.displayname: Small API 28
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6G
fastboot.chosenSnapshotFile: 
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: none
hw.camera.front: none
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:d37b758e1a2b070e348378c2efde849a
hw.device.manufacturer: Generic
hw.device.name: small_phone
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: host
hw.initialOrientation: portrait
hw.keyboard: yes
hw.lcd.density: 320
hw.lcd.height: 1280
hw.lcd.width: 720
hw.mainKeys: no
hw.ramSize: 512
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-28/google_apis/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: no
skin.dynamic: yes
skin.path.backup: /Users/uli/Library/Android/sdk/skins/pixel_3
tag.display: Google APIs
tag.displaynames: Google APIs
tag.id: google_apis
tag.ids: google_apis
vm.heapSize: 32

Steps to Reproduce Bug:

The Mac Arm Pie (API 28) images have a number of problems and look like they need to be reworked. I am entirely unable to use the images because of issue number 3 below, Google Play APIs related to fused location provider look borked. All these issues are the same on Play Store images vs. Play API images.

I re-downloaded the image and its various Play API vs. Store variations and re-created the emulator configuration several times, but it did not make a difference.

None of the other images from API 26 - API 35 have any of these problems. The Pie image is a bad apple. Can you guys rebuild the image somehow?

The display stops updating at times. App continues running normally, but nothing changes on the emulator screen. For example, I start my app manually from the app drawer, and I see it logging normally, but the display continues to just show the app drawer. This issue looks very similar to b/136032206
Arm Pie Images do not work without setting up an SD Card; device startup gets stuck at showing the spinner that is in place prior to showing device.
com.google.android.gms.location.LocationServices.checkLocationSettings throws com.google.android.gms.common.api.ResolvableApiException: 6: RESOLUTION_REQUIRED. A subsequent ResolvableApiException.status.startResolutionForResult does nothing, no error, and nothing on screen. (I don't think this is a problem of display not updating.) I am not able to set location settings manually, accessing anything via the Android Settings UI related to Google Play API location settings seems to hang. This is stuff like whether to use WiFi, Bluetooth, GPS for user location. Essentially my app needs com.google.android.gms.location.Priority.PRIORITY_HIGH_ACCURACY.

Comments

ub...@gmail.com <ub...@gmail.com> #2Jun 22, 2024 06:35PM

I actually was able just now to configure location accuracy manually via the Android settings UI, so my Pie testing is not completely blocked anymore. Still, these Pie issues will keep tripping me up. I hope they can be fixed.

gh...@google.com <gh...@google.com> Jun 26, 2024 03:20AM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> #3Jun 26, 2024 06:43PM

Reassigned to bo...@google.com.

Thanks for your request. We will investigate this issue and see if we can implement the behavior you've requested.

bo...@google.com <bo...@google.com> #4Jun 28, 2024 02:45AM

Accepted by bo...@google.com.

As an additional alternative, it should be possible to specify a label in the options for GmailApp.sendEmail().

A work-around is proposed in StackOverflow:

http://stackoverflow.com/a/18727687/1677912

bo...@google.com <bo...@google.com> #5Jun 28, 2024 02:47AM

Are there any news on adding the ability to archive and add a label to specific emails (not threads)? From a corporate shared mailbox perspective auto threading emails by subject is a serious issue (eg. we recive two emails from the same person with same subject but with different description).

Since it's available in pure mailbox view is that such a big effort to make it available also in Google Script?

bo...@google.com <bo...@google.com> #6Jun 28, 2024 03:25PM

Looking forward to having this implemented. As has been mentioned automatic threading based on subject is a big no-no for our enterprise. We get automated reports and other documents sent to us by customers and suppliers and they are lumped together in threads making it very difficult for me to let Apps Script process them automatically since labels (i.e. outlook folders) have to be applied to entire threads (even though the messages in these threads often need to be treated differently).

ya...@google.com <ya...@google.com> #7Jun 28, 2024 05:27PM

Please add this function (and message.getlabel too) we need to scan message not only the thread.

bo...@google.com <bo...@google.com> #8Jul 2, 2024 07:59PM

Will there be any progress on this issue? Threading is great for humans, but if you are scripting, accessing and manipulating individual messages is MUCH more important, especially if it can be done from the normal user interface. Anything you can do to the thread you should be able to do at the message level.

bo...@google.com <bo...@google.com> #9Jul 2, 2024 08:57PM

Unassigning

homer.apk

2.7 MB

Download

bo...@google.com <bo...@google.com> #10Jul 2, 2024 09:12PM

Activate advanced google services/gmail api and use the gmail api functions.
I have resolved the same issue :)

bo...@google.com <bo...@google.com> #11Jul 3, 2024 06:13PM

Thanks!