Skip to content
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

[Bug]: Wrong pincode at first index of array. There is no types parameter with key postal_code just like google provides in its reversegeocoding API. #257

Open
4 tasks done
prasannakeskar-iprogrammer opened this issue Jan 9, 2025 · 1 comment
Labels
status: needs more info We need more information before we can continue work on this issue.

Comments

@prasannakeskar-iprogrammer

Please check the following before submitting a new issue.

Please select affected platform(s)

  • Android
  • iOS

Steps to reproduce

Hi,

Facing issue of having wrong pincode based on provided devices latitude and longitude. Example, If I am passing device latitude longitude, the accurate postal code should get visible.

Result

Expected Output : 24.8234664, 75.0307014 => 458226

Expected results

If I pass latlong : 24.8234664, 75.0307014 it should get pincode as 458226

Actual results

When passing latlong : 24.8234664, 75.0307014 getting pincode 454226

Code sample

List<geocoding.Placemark> placemarks = await geocoding.placemarkFromCoordinates(loc.latitude, loc.longitude);

Using dart, I should get types as postal-code and basis of that I should get the actual pincode of that location.

Screenshots or video

No response

Version

3.0.0

Flutter Doctor output

Have done all the things and upgraded the flutter version with all other dependencies

@TimHoogstrate
Copy link
Contributor

Dear @prasannakeskar-iprogrammer,

If both platforms are reporting the same Zipcode, I expect it to be correct. However, could you describe if it is happening on iOs and Android?

Kind regards,

@TimHoogstrate TimHoogstrate added the status: needs more info We need more information before we can continue work on this issue. label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs more info We need more information before we can continue work on this issue.
Projects
None yet
Development

No branches or pull requests

2 participants