Android 10: Can not connect to a hotspot with WifiNetworkSpecifier. [143549613]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

pi...@gmail.com

created issue #1

Oct 30, 2019 12:36PM

Since the wifi api is deprecated, I'm trying to implement the new api for android 10 with WifiNetworkSpecifier:
The access point I'm trying to connect to is configured on another device with:

manager.startLocalOnlyHotspot (new WifiManager.LocalOnlyHotspotCallback () {......

A qr code is displayed on this device which contains ssid and wpa passphrase generated automatically and randomly by localOnlyHotspot.

After the qr code scan, here is the code executed on the "client" to connect:

tested on oneplus 7T android 10:

WifiNetworkSpecifier.Builder builder = null;
builder = new WifiNetworkSpecifier.Builder ();
builder.setSsid (ESSID_SECURE);
builder.setWpa2Passphrase (WPA);
WifiNetworkSpecifier wifiNetworkSpecifier = builder.build ();

NetworkRequest.Builder networkRequestBuilder = new NetworkRequest.Builder (); networkRequestBuilder.addTransportType (NetworkCapabilities.TRANSPORT_WIFI);
                        networkRequestBuilder.setNetworkSpecifier (wifiNetworkSpecifier);
NetworkRequest networkRequest = networkRequestBuilder.build ();
                        cm = (ConnectivityManager) explorer.getBaseContext (). getSystemService (Context.CONNECTIVITY_SERVICE);

ConnectivityManager.NetworkCallback networkCallback;
networkCallback = new ConnectivityManager.NetworkCallback () {
                            @Override
                            public void onAvailable (@NoNullNetwork Network) {
                                Log.i ( "network", "ok");
                            }
                            @Override
                            public void onUnavailable () {
                                Log.i ( "network", "failed");
                            }
                        };
cm.requestNetwork (networkRequest, networkCallback);

expected result :
the device connects to the access point after the authorization given by the user who clicks on the pop up window.

obtained result:
The good ssid appears in the window of authorization (after a long delay), and when we click on connect the connection process begins, "recovery of the address ip" then a toast appears "successful connection", logcat gives me " ok "on onAvailable callback but the process starts again with the authorization pop pop up ... and so on.

Here is a video capture of what is happening in link.

This very secure principle works perfectly if targetsdk = 28 with the old deprecated api.

Thank you in advance for giving me some explanations.

https://drive.google.com/file/d/12TVJMsEVhCPuH77r2JmJZwapq_01ZSpo/view?usp=sharing

Comments

sn...@gmail.com <sn...@gmail.com> #2Oct 31, 2019 05:03PM

Thanks for filling this, HiltViewModelFactory wraps around a SavedStateViewModelFactory which is also the default one for non Hilt injected Fragments and Activities, it seems there is some key conflicts, I'll investigate and comer back with more info soon, thanks for the sample app!

sn...@gmail.com <sn...@gmail.com> #3Oct 31, 2019 05:21PM

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

commit d76172ec45a778efe5f46b6ad1a50ae24241d14d
Author: Daniel Santiago Rivera <danysantiago@google.com>
Date: Tue Jun 16 14:50:23 2020

Avoid SavedStateHandle key conflict in HiltViewModelFactory.

When delegating to the SavedStateViewModelFactory to create
ViewModels that are not Hilt injected, the factory will attempt
to retrieve a SavedStateHandler using a controller with the same
key as the SavedStateHandle passed into the abstract create() method
of AbstractSavedStateViewModelFactory for which the
HiltViewModelFactory implements. Therefore causing a key conflict.

In this change we avoid the key conflict collision by prefixing the
before delegating to SavedStateViewModelFactory. Since ViewModels
will be either create by one or the other factory, it is safe to
mangle the key. Meanwhile, even though the key is also used to
add a tag to the ViewModel for cleanup, the tag is only added
if the key used is not present. When SavedStateViewModelFactory
tags the ViewModel and then a second time in once
AbstractSavedStateViewModelFactory#create() returns, the tag
is not overridden (lucky us).

This fixes a bug when mixing vanilla ViewModels and Hilt injected
ones.

Bug: 158737069
Test: ViewModelApp Integration Tests
Change-Id: I86ae254c2f26795c900317d42041319fd279e545

M buildSrc/src/main/kotlin/androidx/build/LibraryVersions.kt
M hilt/hilt-lifecycle-viewmodel/src/main/java/androidx/hilt/lifecycle/HiltViewModelFactory.java
M hilt/integration-tests/viewmodelapp/build.gradle
A hilt/integration-tests/viewmodelapp/src/androidTest/java/androidx/hilt/integration/viewmodelapp/ActivityInjectionTest.kt
A hilt/integration-tests/viewmodelapp/src/androidTest/java/androidx/hilt/integration/viewmodelapp/BaseActivityInjectionTest.kt
A hilt/integration-tests/viewmodelapp/src/androidTest/java/androidx/hilt/integration/viewmodelapp/BaseFragmentInjectionTest.kt
A hilt/integration-tests/viewmodelapp/src/androidTest/java/androidx/hilt/integration/viewmodelapp/Bindings.kt
A hilt/integration-tests/viewmodelapp/src/androidTest/java/androidx/hilt/integration/viewmodelapp/FragmentInjectionTest.kt
A hilt/integration-tests/viewmodelapp/src/androidTest/java/androidx/hilt/integration/viewmodelapp/MyViewModels.kt
A hilt/integration-tests/viewmodelapp/src/androidTest/java/androidx/hilt/integration/viewmodelapp/TestRunner.kt
A hilt/integration-tests/viewmodelapp/src/debug/AndroidManifest.xml

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

ry...@gmail.com <ry...@gmail.com> #4Oct 31, 2019 06:27PM

A fix for this will be available in alpha02

pi...@gmail.com <pi...@gmail.com> #5Nov 1, 2019 11:09AM

#3
"Added article content,Fixed article typos,Optional artiCB le contents link,Any other way to improve this article"

What do you mean?

am...@google.com <am...@google.com> #6Nov 4, 2019 06:33AM

Assigned to am...@google.com.

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

Increase the bugreport size to 16MB to not miss any logs. change it here : settings -> system -> Developer options -> Logger buffer sizes.
To enable developer options, click on build number till you see the toast. (Settings -> about phone -> build number)

To capture bug report:
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

Note: Please place the bug report in a folder, upload it to google drive and share the folder to android-bugreport@google.com, then share the link here.

pi...@gmail.com <pi...@gmail.com> #7Nov 4, 2019 07:59AM

Here is a log capture of what is happening in link.

https://drive.google.com/file/d/1FlkBFZ_WAuHfVSvpCgO04XqHDnyJwEw_/view?usp=drive_web (log_wifispecifier.txt)

am...@google.com <am...@google.com> #8Nov 6, 2019 06:18AM

The logcat file shared here does not have necessary logs to debug. Please do follow the above procedure to capture the report and share.

pi...@gmail.com <pi...@gmail.com> #9Nov 6, 2019 11:46AM

On the one plus 7T volume down + volume up + power launches a screenshot ...

The log file you want contains FS and proto directories?

pi...@gmail.com <pi...@gmail.com> #10Nov 12, 2019 10:46AM

Please ,
can you give me more explanations on the procedure to follow?

am...@google.com <am...@google.com> #11Nov 15, 2019 11:25AM

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, 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.

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

am...@google.com <am...@google.com> #12Nov 22, 2019 10:18AM

Please note it’s hard to proceed further on the issue without the required info. Unfortunately the issue would be closed within 7 days if there is no further action on the requested info.

am...@google.com <am...@google.com> #13Nov 29, 2019 10:49AM

We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

am...@google.com <am...@google.com> #14Dec 3, 2019 09:40AM

Looks like the app is releasing the network request immediately after connecting to the network and then re-initiating a new request. The app needs to hold on to the request as long as they want to stay connected to their network.

11-04 08:48:46.257 1518 2001 D WifiNetworkFactory: Connected to network * ID: -1 SSID: "AndroidShare_1814" PROVIDER-NAME: null BSSID: 8e:f5:a3:0d:d0:2c FQDN: null PRIO: 0 HIDDEN: false PMF: false OWE Transition mode Iface: null
...
11-04 08:48:46.384 1518 2001 I WifiNetworkFactory: App released request, cancelling NetworkRequest [ REQUEST id=97, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Specifier: <WifiNetworkSpecifier [, SSID Match pattern=PatternMatcher{LITERAL: AndroidShare_1814}, BSSID Match pattern=Pair{00:00:00:00:00:00 00:00:00:00:00:00}, SSID="AndroidShare_1814", BSSID=null, requestorUid=10291, requestorPackageName=com.techniwork.fastsharing]> Uid: 10291] ]
11-04 08:48:46.384 1518 2001 I WifiNetworkFactory: Disconnecting from network on reset
...
1-04 08:48:51.672 1518 2001 D WifiNetworkFactory: User initiated connect to network: "AndroidShare_1814"
11-04 08:48:53.541 1518 2001 D WifiNetworkFactory: Connected to network * ID: -1 SSID: "AndroidShare_1814" PROVIDER-NAME: null BSSID: 8e:f5:a3:0d:d0:2c FQDN: null PRIO: 0 HIDDEN: false PMF: false OWE Transition mode Iface: null
11-04 08:48:53.541 1518 2001 D WifiNetworkFactory: NetworkSelectionStatus NETWORK_SELECTION_ENABLED
...
11-04 08:48:53.644 1518 2001 I WifiNetworkFactory: App released request, cancelling NetworkRequest [ REQUEST id=97, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Specifier: <WifiNetworkSpecifier [, SSID Match pattern=PatternMatcher{LITERAL: AndroidShare_1814}, BSSID Match pattern=Pair{00:00:00:00:00:00 00:00:00:00:00:00}, SSID="AndroidShare_1814", BSSID=null, requestorUid=10291, requestorPackageName=com.techniwork.fastsharing]> Uid: 10291] ]
11-04 08:48:53.644 1518 2001 I WifiNetworkFactory: Disconnecting from network on reset

am...@google.com <am...@google.com> Dec 5, 2019 04:30AM

Marked as fixed.

th...@netatmo.com <th...@netatmo.com> #15Dec 31, 2019 02:47PM

Hi (=

I was wondering if there was a known date for a release containing this fix?

We are still experiencing this issue with OnePlus devices - 10.0.3.GM21BA - preventing some users to install IoT products relying on this new API.

If the AOSP patch is already available it might be on OnePlus side now.

re...@gmail.com <re...@gmail.com> #16Feb 7, 2020 08:51AM

Still experiencing on OxygenOS Open Beta 8, OP7 pro

[Deleted User] <[Deleted User]> #17Feb 24, 2020 11:37AM

We are still experiencing this issue with OnePlus devices - 10.0.4.GM21BA

pi...@gmail.com <pi...@gmail.com> #18Mar 2, 2020 02:09PM

Still experiencing on OxygenOs OnePlus 7T device 10.0.8.HD65BA.

My bug report file:

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

pi...@gmail.com <pi...@gmail.com> #19Mar 2, 2020 02:19PM

"Looks like the app is releasing the network request immediately after connecting to the network and then re-initiating a new request. The app needs to hold on to the request as long as they want to stay connected to their network."

what does that mean?

ip...@gmail.com <ip...@gmail.com> #20Apr 25, 2020 05:05PM

I am also seeing this exact issue on OnePlus 8 device 10 10.5.2.IN21BA

ip...@gmail.com <ip...@gmail.com> #21Apr 25, 2020 05:27PM

I've filed a bug report also, including a screen recording showing the issue, available here:

https://drive.google.com/drive/folders/107Di-fMWYZWTkUIRxj_kZZ0qniA-JgDK?usp=sharing

ip...@gmail.com <ip...@gmail.com> #22Apr 25, 2020 06:34PM

See also the following posts flagging the same issue:

https://stackoverflow.com/questions/59984518/android-q-wifinetworkspecifier-loosing-wifi-immediately-after-connection-is-est?answertab=active#tab-top

https://stackoverflow.com/questions/59400614/can-not-establish-wifi-connection-android-api29/61429557#61429557

2n...@gmail.com <2n...@gmail.com> #23May 1, 2020 06:28AM

me too getting the same issue

qc...@gmail.com <qc...@gmail.com> #24May 4, 2020 05:04PM

Same here, OP7 Pro

ip...@gmail.com <ip...@gmail.com> #25May 30, 2020 09:19AM

Is there any way to re-open this, as it's clearly not 'fixed'?

pi...@gmail.com <pi...@gmail.com> #26Jun 16, 2020 11:01AM

Fixed for me with OTA update 10.0.11.HD65BA Oneplus 7T .

ip...@gmail.com <ip...@gmail.com> #27Jun 16, 2020 11:03AM

Fixed for me with OTA update 10.5.7.IN21BA OnePlus 8

el...@gmail.com <el...@gmail.com> #28Aug 17, 2020 12:47PM

Will this get fixed on Oneplus 7?

to...@googlemail.com <to...@googlemail.com> #29Aug 29, 2020 08:20PM

I am still experiencing this exact issue on OnePlus 8 pro device 10.5.8.IN11BA

ve...@gmail.com <ve...@gmail.com> #30Sep 2, 2020 07:01AM

I am still experiencing this exact issue on HUAWEI Mate 30 pro 5G LIO-AN00 10.1.0.152(COOE136R6P2)

ba...@gmail.com <ba...@gmail.com> #31Sep 9, 2020 07:03AM

I'm still having issues with this which blocks us from connecting to a smart device to set it up. Only restarting phone helps but it is not really convenient that we tell all users who have Android 10 to restart their phones to be able to connect to a smart device.
Some of the phones that I found to be affected by this are:
Samsung S20
Samsung S10
Samsung S9
OnePlus 8 Pro

All of them on Android 10.

br...@gmail.com <br...@gmail.com> #32Sep 9, 2020 07:08AM

This issue hasn't been fixed. When trying to connect to wifi with Samsung S9 or S20 there are two unwanted outcomes that I have experienced:
1. Clicking on SSID does nothing, and error message is shown after some time
2. Connecting to wifi works 3 times (with proper unregistering), but gives error 4th time

bo...@infinum.com <bo...@infinum.com> #33Sep 9, 2020 07:08AM

This doesn't really work on Android 10, can confirm.

[Deleted User] <[Deleted User]> #34Sep 9, 2020 07:14AM

A lot of issues with this one so I can confirm that it's not fixed.

ik...@gmail.com <ik...@gmail.com> #35Sep 9, 2020 09:52AM

I can confirm this is not fixed.

se...@gmail.com <se...@gmail.com> #36Oct 9, 2020 03:28PM

New issue https://issuetracker.google.com/u/1/issues/170406306

dr...@gmail.com <dr...@gmail.com> #37Jan 7, 2021 07:34PM

Hello Google,

I have been using 2018 Samsung Galaxy A7 having android 10 at present,since about 2 years and haven't faced any issues with the android device except one major problem that it doesn't allow data to be backed up to my new iPhone 12 having IOS 14.3.

So while using the MOVE TO IOS application,the android device shows CONNECTION SUCCESSFUL ,then AUTHENTICATION also works but after that in preparing stage it fails and recive the message on my android that NO IOS DEVICE FOUND.....At the same time I receive the message on my apple device that UNABLE TO MIGRATE.

On contacting apple I found out that there is some issue with android plateform owned by Google and there are several people like me waiting for the resolution.

I hope we ll get the earliest resolution of the issue mentioned above.

Thanks and regards...
Dr.Manthan Solanki.

br...@infinum.com <br...@infinum.com> #38Jan 28, 2021 02:04PM

Still not working. Tested on Pixel 2 (Android 11).

fl...@gmail.com <fl...@gmail.com> #39Feb 10, 2021 02:32PM

Yup, this still doesn't work. Confirmed on Pixel 4 XL (Android 11).

mu...@gmail.com <mu...@gmail.com> #40Mar 23, 2021 05:53PM

Hello,

I came here because Apple Support directed me to do so.

My issue is that I couldn’t transfer older phone (huawei p30 lite) to newer phone (iphone 11). We followed few different ways however found out that this is a common issue. I don’t know when it might be solved, or even will google be able to solve..

I wanted to raise hand as an aggrieved.

Take care,

mj...@hotmail.com <mj...@hotmail.com> #41Jun 23, 2021 06:16AM

Buenos días estoy con el mismo problema que esta persona. Lo copio como lo pone. ¿sabéis si ya se ha solucionado por favor? Muchas gracias.
Mª José

"Hola Google,
He estado usando 2018 Samsung Galaxy A7 con Android 10 en la actualidad, desde hace aproximadamente 2 años y no he enfrentado ningún problema con el dispositivo Android, excepto un problema importante que no permite hacer una copia de seguridad de los datos en mi nuevo iPhone 12 con IOS 14.3.
Entonces, mientras usa la aplicación MOVE TO IOS, el dispositivo Android muestra CONNECTION SUCCESSFUL, luego AUTHENTICATION también funciona, pero luego de eso, en la etapa de preparación falla y recibe el mensaje en mi Android que NO SE ENCONTRÓ UN DISPOSITIVO IOS ..... Al mismo tiempo recibir el mensaje en mi dispositivo Apple que NO SE PUEDE MIGRAR. Al ponerme en contacto con Apple, descubrí que hay algún problema con la plataforma de Android propiedad de Google y hay varias personas como yo esperando la resolución. Espero que obtengamos la resolución más temprana del problema mencionado anteriormente.
Gracias y saludos.
Dr.Manthan Solanki."

ak...@gmail.com <ak...@gmail.com> #42Jul 30, 2022 04:44PM

for who has this issu, if you connectd to this AP before try to go to the wifi list on your mobile then click a long click on the networke with issu then click on (Forget this network) then try to connect it will connect i hope

fr...@gmail.com <fr...@gmail.com> #43Aug 5, 2022 06:58AM

networkCallback = new ConnectivityManager.NetworkCallback () {
@Override
public void onAvailable (@NoNullNetwork Network) {
Log.i ( "network", "ok");
cm.bindProcessToNetwork(network)
}