Infeasible
Status Update
No update yet.
Comments
vi...@google.com
for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?
i donnot understand why is the data the same?
ma...@hypr.com
the fractional part of the location data is exactly the same.
vi...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. AP4A.241205.013.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
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.
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 bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. AP4A.241205.013.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
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.
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 android-bugreport@google.com, then share the link here.
vi...@google.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
vi...@google.com
I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。
as for Android build,all versions have it.
I dont reprodouce this issue.
what may be the cause of this issue?please
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。
as for Android build,all versions have it.
I dont reprodouce this issue.
what may be the cause of this issue?please
Description
After a lot of debugging, we found a issue that needs the combination of android 15 and Chrome 131 (android mobile app).
Our flow is the following:
- start a login flow from chrome app using okta, starts a long polling request
- auth request triggers our android app
- android app verifies if auth is correct and goes through if yes, calling server to validate
- server validates and app shows success
- chrome tab is back on the foreground and long polling request initially created receive success
For android 14 + Chrome 131, the long polling request sustains as the chrome tab is put in the background as the android native auth app is opened, and the flow works
For android 15 + Opera 85 (based on chromium 129), same thing, the flow works
For android 15 + Chrome 131, the long polling request is terminated few seconds after the chrome tab is put in the background as the android native app opens. When the auth is accepted on the app, then we're back on the chrome tab, the POST request has long been killed, and try to restart the flow instead of accepting the auth. Indeed, the server can't reach that request anymore.
Here are some Charles proxy screenshot, one from Chrome 131 and one from Opera 85, both on android 15 (pixel 7 pro). You can see that the POST long polling request lasts 57seconds on Opera, but it's killed after 9 seconds on Chrome.
On android 14 and Chrome 131, this flow worked as the request is not killed when put in background.
My educated guess would be a special optimisation on android 15 + Chrome 131 to kill requests that are still open in the background. Or maybe a security feature to avoid such background request ? Anyway, it's a major issue for our users as android 15 is getting widely adopted since its recent release.