-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined error message returning from catch (getCurrentPosition) #260
Comments
Why do you use a version from 1.5 years ago? See changelog See LocationError in the API docs to learn what code |
Hey, thanks for the quick reply.
We have too many dependencies (plugins), some of them can generate a lot of trouble if we initiate this quest to update the capacitor version, so i have to convice a lot of people to make this happen.
Yes, thank you, i just now read it, and the following lines could be related: If you say to me that updating this plugin version will solve this problem, no need for more discussion, I will make this happen and send you an update <3
Yes, yes, I know what this error means, the problem is that I have to make this error shows on the catch phase, so I can show the adequate error message to the user, so them can know what to do next. |
.onLocation accepts a 2nd argument onLocationError, which you’ll find is receiving the error. See api docs .onLocation |
Ok! I will give it a try and update back to you in a moment, thanks for the quick support. |
You could try setting |
Hey, the logs on the description of the issue is the debug logs when I run the simulation of the bug |
Exemple of logs when the problem occurs. The problem is not the error itself, i manualy disable the location service to throw this error. The problem is that the error callback only returns This is a problem becouse our users dont know what to do when that happens, contacting customer service every time. |
Google Play requires SDK version 34 now, this is the perfect excuse to us to update our app, we will work on that on next month. I will exepect that this bug is a problem with the current old version that we use, if the latest version still have this bug, I will communicate here on the end of the next month <3 |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Your Environment
npx cap doctor
)#ready
:Expected Behavior
Error message throwed by plugin, and not 'undefined'
Actual Behavior
Plugin throws 'undefined' on any error
Steps to Reproduce
The code:
Context
Ask me more questions if this is not clear enougth
Debug logs
What happens when we turn off location on android
Logs
The text was updated successfully, but these errors were encountered: