Device Setup: Can't connect to device WiFi on Android 10 #92
Comments
|
Hello @rduriancik, thank you for reporting this. Not sure if this will get looked into before the holiday, but @jensck (he maintains this repo) will return to you as soon as he sees this. |
|
I've confirmed this. Clearly this needs to be solved for the long term, but in the short term, have you shipped your app with API 29 yet? If not, as a temporary workaround, can you target API 28 instead? |
|
Yes, we already shipped our app with API 29. We have customers using Google Pixel phones and some other OEMs are also rolling Android 10 out. |
|
Okay, thanks for the follow up. I'll to start looking at an alternative approach that works when targeting API 29. |
|
Update: I'm back from the holiday break. Finding a suitable approach for API 29 is one of my immediate top priorities. I'll post another update later this week with what I've found. |
|
I should be shipping an update to the setup lib this week which addresses this. |
|
@rduriancik I wanted to give you a heads up that this fix will be delayed due to shifting team priorities. You'll have to keep using the workaround of targettting API 28. |
|
No worries, we don't need it anymore but thank you. |
|
@rduriancik I've got the same problem. Did you manage to solve the issue? |
|
@markoImake No, I don't. We stopped using particle. |
|
@monkbroc is there any update on when the fix for this will be released? |
|
There is no update yet beyond using the workaround of targetting API 28 for now. |
|
@monkbroc @jensck Do you have any update on this issue? Next month (November 2020) we won't be able to use the workaround of targeting API 28 anymore, so essentially we won't be able to release any app updates while supporting this Particle device setup feature - https://developer.android.com/distribute/play-policies |
|
Yes, we are testing a fix right now. I'm hoping we can share the pull request by the end of the week. |
|
@monkbroc thanks for the update, we will be very interested in viewing the pull request once available. |
|
@markoImake can try try the branch |
|
@monkbroc I have tested that branch and can confirm it works, thanks! I also experienced the issue you mentioned. Do you have any idea when the issue will be resolved? |
|
@monkbroc @jensck I have tested the new Android 10/11 device setup on a few different devices and have run into a case where it is not working. When using a OnePlus 6 device I experience some unexpected behaviour. See logcat error below and device info and video showing behaviour attached. Please let me know if you need any further information.
|
|
Hi @markoImake. The device setup lib update with support for API 29 and beyond was released yesterday. https://github.com/particle-iot/particle-android/releases/tag/devicesetup-0.7.0 We haven't seen the issue you posted above in our testing. The exception shows it is unable to get the device ID during setup, which is not an area of the code that has changed and shouldn't be a model-specific issue. Does it occur every time, on every device with this particular model of phone? |
|
@monkbroc The issue occurs every time on every particle device using that particular phone. I happened to have access to another phone of the same model and found that it is working fine, so the issue does seem limited to that one particular phone. Interestingly it works perfectly with the old device setup library. |
|
Maybe it's got something to do with the data in the app? Does the issue
occur after you clear the data and/or reinstall the app?
…On Sun, Nov 1, 2020, 8:02 PM markoImake ***@***.***> wrote:
@monkbroc <https://github.com/monkbroc> The issue occurs every time on
every particle device using that particular phone. I happened to have
access to another phone of the same model and found that it is working
fine, so the issue does seem limited to that one particular phone.
Interestingly it works perfectly with the old device setup library.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOUVQPJPHNXHH7YKRYLG2LSNYALTANCNFSM4J3MGJNQ>
.
|
|
I'll mark this issue closed. If you find more info about the phone that was having issues please open a new issue, ok? |
Hi, I have an issue on Android 10 to connect to our device on the DeviceDiscovery screen. We use a slightly modified version of your library but the business logic is almost the same. I debugged it and probably got to the main problem.
connectToAp(...)method in ApConnector calls WifiManager (via WifiFacade)addNetwork(...)method and if that fails it also callsgetConfiguredNetworks(...)ingetWifiConfiguration()method of WifiFacade. Both these methods are deprecated on Android Q and according to the doc, for Android Q and aboveaddNetwork()returns -1 andgetConfiguredNetworks()returns an empty list.I found a similar issue on StackOverflow but with no particular answer https://stackoverflow.com/questions/56905956/is-it-possible-to-add-a-network-configuration-on-android-q.
Have you been able to solve this?
The text was updated successfully, but these errors were encountered: