Adobe-Runtime-Support
Adobe-Runtime-Support copied to clipboard
URLLoader API calls FAILING (IO error #2032) on Android 14
We have a client-facing app that heavily relies on HTTPS calls to our api. Using BrowserStack to test on Google Pixel 8 phones running Android 14, calls are failing with IO error #2032.
Android 13 and below appears to be working fine.
This will become a major issue as adoption of Android 14 picks up.
We develop with Flex/AS3 AIR in IntelliJ, using its build tools (no custom command line actions). AIR SDK 2.4.2 and 2.3.6 produced same result. Testing with a simple URLLoader with URLRequest will reproduce the issue. Example URL - https://cat-fact.herokuapp.com/facts/
Hi
We just checked on the Android emulator (Pixel 6 Pro, Android 14 / API 34) and an HTTPS url request worked fine .. likewise via AWS Device Farm, on a Pixel 7 Android 14.
So this may be related to BrowserStack? If you send us an APK, we can check it via these other platforms?
thanks
Thank you, please see our test app attached. Main.apk.zip
Screenshot of ioError from BrowserStack on a Google Pixel 8 Android 14.
Thanks. I uploaded that to a Pixel 7 arm64 device in AWS and it worked fine.. not sure if this means there's something different in a Pixel 8, or if it's specific to BrowserStack. When you said it worked on Android 13, was this also tested via BrowserStack? (and do you have an option to also use a Pixel 8 on BrowserStack with Android 13?!)
thanks
I appreciate you checking. This is the list of Google devices available to me. The app errors on every device here on Android 14. And yes, all of my Android testing has been through BrowserStack.
I suppose it is a good sign that you have not seen the error, which does point to BrowserStack setup. The Pixel 6 Pro on 14 did give me the error, so it's not just the 8 phone. This only points to the Android 14 being the common factor across devices on this site.
Just an FYI: my app which also heavily relies on HTTPS calls to our API works fine on my Pixel 7 Android 14 device. So perhaps its further evidence that it is a BrowserStack issue, not an Air one.
Just an FYI: my app which also heavily relies on HTTPS calls to our API works fine on my Pixel 7 Android 14 device. So perhaps its further evidence that it is a BrowserStack issue, not an Air one.
Thank you for looking at this. I'm following up with BrowserStack support and having them investigate further.
Any new on that ?
I am also facing the same issue when testing my app via Browserstack. on all devices with Android 14 I get http errors and the application is stuck. with lower version everything is ok.
I apologize for not following up. I did hear back from BrowserStack last month regarding their investigation into the issue. Their conclusion is that this is a fault with the SDK's operation within their proxy configuration. They suggest the SDK in other proxy environments may behave the same way. See their response below.
.......... We have some findings to share with you:
-
We would like to inform you that we have a cascading Proxy configuration enabled on all the real devices within our BrowserStack infrastructure. This is required to support our implementation and testing on BrowserStack. Unfortunately, we cannot disable this due to our implementation on BrowserStack.
-
We tested your app and found that it works perfectly fine with the Proxy disabled on the Google Pixel v14 devices. However, the same URL that the app is loading is working perfectly on Chrome, Firefox, the other Android v13 and below devices, and in the Java build Android app with Proxy enabled on the same device but fails only with your app on Android v14 device.
-
Based on this investigation, It appears that this issue is specific to the SDK of your app that's not respecting the Proxy configuration on the Google Pixel 8 v14 devices. To further debug this issue, we suggest that you configure Charles proxy or any proxy on a local Android v14 device and test your app which should show the same results.