Emulator -dns-server option does not work after API 31 [249366543]

Fixed

Bug

Status Update

No update yet.

Description

ws...@gmail.com

created issue #1

Sep 28, 2022 12:57AM

DESCRIBE THE ISSUE IN DETAIL: The emulator CLI's -dns-server option does not seem to work on API 31 or newer.

STEPS TO REPRODUCE:

Run a local dns server and log queries: dnsmasq -dq
Start an API 31 emulator: emulator -avd emulator31 -dns-server 127.0.0.1
Resolve a domain: adb shell ping www.reddit.com
dnsmasq does not show that domain in the log.

However, on API 30, these same steps will result in the dnsmasq showing the queries to reddit.com:

dnsmasq: query[A] www.reddit.com from 127.0.0.1
dnsmasq: forwarded www.reddit.com to <ip>
dnsmasq: reply www.reddit.com is <CNAME>
dnsmasq: reply reddit.map.fastly.net is <ip>

We need to override some DNS entries in order to test our app in environments that do not have external internet access, but it stopped working in API 31 or newer.

Comments

ws...@gmail.com <ws...@gmail.com> #2Sep 28, 2022 04:44PM

After creating the issue I've noticed that I mixed up a few terms, sorry about that. JobService should be JobScheduler. When referring to jobs in the description, those are classes extending Worker.

pa...@google.com <pa...@google.com> Sep 29, 2022 12:52AM

Assigned to an...@google.com.

ws...@gmail.com <ws...@gmail.com> #3Sep 29, 2022 01:03AM

We have a large set of users seeing this same issue... I can confirm that it seems to only effect users using Android OS 4.4 - 5.1. We are also using WorkManager 2.0.0

bo...@google.com <bo...@google.com> Oct 5, 2022 06:53PM

Reassigned to wd...@google.com.

wd...@google.com <wd...@google.com> #4Oct 14, 2022 03:03PM

Accepted by wd...@google.com.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 098c163581a360c32baa6e4c215227f0efd10889
Author: Rahul Ravikumar <rahulrav@google.com>
Date: Mon Mar 25 14:05:34 2019

Reset WorkConstraintsTracker when cleaning up in DelayMetCommandHandler.

* DelayMetCommandHandler would previously not cleanup correctly and WorkConstraintsTracker
would trigger callbacks without going through the SystemAlarmDispatcher lifecycle
of processing a command.

Fixes:

b/129226383

Test: Added a unit test.
Change-Id: Id2aaf0cce7c4a1a4526a25a211f3fe0551dbe557

M work/workmanager/src/androidTest/java/androidx/work/impl/background/systemalarm/SystemAlarmDispatcherTest.java
M work/workmanager/src/main/java/androidx/work/impl/background/systemalarm/DelayMetCommandHandler.java

https://android-review.googlesource.com/933140

https://goto.google.com/android-sha1/098c163581a360c32baa6e4c215227f0efd10889

wd...@google.com <wd...@google.com> #5Oct 17, 2022 07:45PM

Marked as fixed.

Great to see such a quick fix. Do you have any estimate when a new version that includes this change will be released?

jo...@inspiretek.io <jo...@inspiretek.io> #6Oct 18, 2022 02:44AM

It should be available in the next 2.x.x version.

wd...@google.com <wd...@google.com> #7Oct 18, 2022 02:27PM

ETA?

wd...@google.com <wd...@google.com> #8Oct 27, 2022 05:59PM

Hi, we have implemented a new big feature using WorkManager and got the same issue. We have been considering third party alternatives because we need to deliver this ASAP. But if you confirm that we will have that version within next few days we can wait for it.