Unable to get geo point data, table is empty

Are you looking for help?

This is a support forum for reporting issues related to Backendless services. Please note that due to our support policy we cannot provide you help with debugging your code, consulting in regards to any language or third-party library usage. For this kind of questions we recommend using more appropriate forums like Stack Overflow.

In order to suggest you a quality solution, we shall usually ask you to provide the details mentioned below first. Including them into your topic right away helps us to start investigating your issue much faster.

In case you have a suggestion or an idea, the details below are not always required, though still any additional background is welcome.

Backendless Version (3.x / 5.x, Online / Managed / Pro )

5.6.0 (iOS Cocoapods)

Client SDK (REST / Android / Objective-C / Swift / JS )

  • Backendless (5.6.0):

Application ID

CAE2F747-3974-8ADF-FF4A-61AC85D5AF00

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. We had out geo points stored in DB using iOS SDK code: backendless?.geoService.save
  2. Then we used to get nearest geo points using following code:
    backendless?.geoService.getPoints
  3. Now our database is empty, and also #2 method is not getting called. We had few records in our table.
  4. We should have our data and #2 should get called

Actual Behavior

Please provide a description of what actually happens, working from the same starting point.

Be descriptive: “it doesn’t work” does not describe what the behavior actually is – instead, say “the request returns a 400 error with message XXX”. Copy and paste your logs, and include any URLs.

  1. We had out geo points stored in DB using iOS SDK code: backendless?.geoService.save
  2. Then we used to get nearest geo points using following code:
    backendless?.geoService.getPoints
  3. Now our database is empty, and also #2 method is not getting called. We had few records in our table.
  4. We should have our data and #2 should get called

Reproducible Test Case

Please provide a simple code that could be run in a new clean app and reproduce the issue.

If the issue is more complex or requires configuration, please provide a link to a project on Github that reproduces the issue.

Hello @Paul_Nadeau

Welcome to the community and thanks for posting this question!

Seems like you are referencing to the Old GEO Service which has been replaced by a new one (Spatial Data Types) a long time ago and the legacy GEO service has been removed almost a year ago, and we’ve been notified many times all our customers about this.

Regards, Vlad