Status Update
Comments
sh...@xerox.com <sh...@xerox.com> #2
Typo error on my problem statement: User is unable to connect with Wi-Fi network initially, but after few attempts we are getting "No devices found. Make sure devices are turned on and available to connect."
vi...@google.com <vi...@google.com> #3
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
sh...@xerox.com <sh...@xerox.com> #4
Prerequisite to use sample app: Need any WIFI network with WPA2
Steps to be followed:
1) Enter Wifi network name in Enter SSID field
2) Enter Password of the Wifi network in Password field
3) Click Connect WiFi button
4) Android Framework will be prompted . You to click "Connect" button to join on Wifi network.
5) Then close the application and remove it from recent app aswell
6) Repeat the steps from 1 to 5 for 5 more times.
7) You will see App will not connect to the network after few attempts.
Sample source code link:
sh...@xerox.com <sh...@xerox.com> #5
vi...@google.com <vi...@google.com> #6
Thanks for the above information, please provide the access to the drive link.
sh...@xerox.com <sh...@xerox.com> #7
fa...@gmail.com <fa...@gmail.com> #8
vi...@google.com <vi...@google.com> #9
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
m....@gmail.com <m....@gmail.com> #10
Sure. Please confirm are you guys able to reproduce this issue?
What is expected time taken reply from Product & engineering team?
na...@gmail.com <na...@gmail.com> #11
vi...@google.com <vi...@google.com> #12
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
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 bug report and screenshot to google drive and share the folder to
qa...@gmail.com <qa...@gmail.com> #13
We will describe the details in this issue.
Please let us know if you would like to register a new issue.
・Source code
Same as #1
・Procedure
ConnectivityManager.requestNetwork to connect to SoftAp, then unregister with ConnectivityManager.unregisterNetworkCallback.
The phenomenon occurs when the above is repeated multiple times.
When this occurs, the error log is not output and NetworkCallback's onAvailable is not called.
・How to recover
Turn off the Android device and then turn it back on.
It is not possible to recover by uninstalling and installing the application.
・Terminals where defects occur
Android13 : Pixel6a, Pixel5
Android12 : Pixel6a, Pixel6
sh...@xerox.com <sh...@xerox.com> #14
vi...@google.com <vi...@google.com> #15
The development team has fixed the issue and it will be available in a future build.
sh...@xerox.com <sh...@xerox.com> #16
li...@gmail.com <li...@gmail.com> #17
ha...@pushtech.dev <ha...@pushtech.dev> #18
(Build number TQ2A.230405.003.E1)
m....@gmail.com <m....@gmail.com> #19
Is the fix for this issue released?
Could you please share the build number of this issue fix available to public.
sh...@xerox.com <sh...@xerox.com> #20
Could you please share the build number of this issue fix available to public.
st...@gmail.com <st...@gmail.com> #21
qa...@gmail.com <qa...@gmail.com> #22
Could you please tell me what you fixed (OS, Android system components, etc.).
I would also like to know in which version you fixed it.
pg...@we-o.com <pg...@we-o.com> #23
vi...@google.com <vi...@google.com> #24
This will be released with June mainline update. Thanks!
eh...@gmail.com <eh...@gmail.com> #25
qa...@gmail.com <qa...@gmail.com> #26
Is it correct to recognize that it was commented to be released in June, but it has not been released yet?
I would also like to know if you have any information about the release date and the modification of the glitch.
vi...@google.com <vi...@google.com>
kc...@viessmann.com <kc...@viessmann.com> #27
vi...@google.com <vi...@google.com> #28
This fix has been released with the June Google Play system update.
Please check your device with settings > about phone > Android version > Google play system update.
This will be released gradually.
eh...@gmail.com <eh...@gmail.com> #29
The requestnetwork function of the connection manager is not working after a while. I have to click on fix connection button in wifi settings screen or reset wifi..
bi...@codespring.ro <bi...@codespring.ro> #30
We were able to implement a workaround by not unregistering the network callback for Android 13. It's not an ideal solution, but looks like it fixes the problem until Google fixes the root cause.
ri...@mercedes-benz.com <ri...@mercedes-benz.com> #31
Have installed July Version, but still I am not able to connect after the first time.
This bindProcessToNetwork(network) is not blocked and hence the Wifi is not connecting.
Still not fixed. If it is fixed kindly provide the patch version which is providing the fix.
Thanks
kc...@viessmann.com <kc...@viessmann.com> #32
ts...@gmail.com <ts...@gmail.com> #33
I also still see the problem. From my observation, what I am experiencing is that the wifi scan that is triggered by connectivityManager.requestNetwork() never finishes and returns results. That leads to the connection never happening and leaves the app waiting for the process to finish. My thoughts is that there is some sticky state that is preventing the wifi scan from completing properly. Sometimes, toggling the wifi or resetting the wifi temporarily fixes the issue. Sometimes a full restart is required.
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #34
Thanks again for the feedback! Our product and engineering teams have evaluated the request and responded:
Please provide a bugreport, We have tested in our local everything that works as intended.
Please check
Also the network request is for local only connection which doesn't have an internet connection.
Also for the device support STA+STA, the connection will not be user visible, as it will not affect the internet connection for the user.
eh...@gmail.com <eh...@gmail.com> #35
vi...@google.com <vi...@google.com> #36
For further investigation, we would need the information requested in
vi...@google.com <vi...@google.com> #37
The issue has been fixed and should be available with Google play system update August 1, 2023.
fa...@gmail.com <fa...@gmail.com> #38
The latest version now is July 1, 2023, the problem still exists.
When can I receive the August 1 version?
vi...@google.com <vi...@google.com> #39
Thanks for the above information, we will check with our engineering team and will provide an update once it becomes available.
vi...@google.com <vi...@google.com> #40
Our Engineering team is still working on this issue. We will provide more updates as they become available.
ar...@gmail.com <ar...@gmail.com> #41
Dear Team,
I can provide some guidance regarding when the connection is established and when it is not. If the Networkcallback returns "Unavailable" for the requested Wi-Fi network, please navigate to the Wi-Fi settings page from the status bar to verify if the desired Wi-Fi network is listed there. Afterward, return to the application and attempt the connection once more. By following this process, the requested network will be connected promptly.
In summary, refreshing the Wi-Fi settings page and then attempting to connect with the Wi-Fi network consistently yields successful results in Android API S_V2 (32) and 33 (TIRAMISU).
Hope this is helpful to find out the root cause.
Description
WifiNetworkSpecifier wifiNetworkSpecifier = new WifiNetworkSpecifier.Builder()
.setSsid(<SSID>)
.setWpa2Passphrase(<Password>)
.setIsHiddenSsid(true)
.build();
NetworkRequest networkRequest = new NetworkRequest.Builder()
.addTransportType(NetworkCapabilities.TRANSPORT_WIFI)
.setNetworkSpecifier(wifiNetworkSpecifier)
.build();
connectivityManager.requestNetwork(networkRequest, networkCallbacks);
We are seeing this issue only on Google Pixel 4(Android 13) device.
Same code is working fine Pixel 4 Android 12 device.