Replit told me to hire an outside developer for problem my Replit agent created

Bugs
, ,
1

HELP, please. I am new to this. I designed an app in a few months, got approved by Apple, and am now stuck in a loop hat my Replit Agent, and Replit, cannot fix. And I cannot understand why.

I have been trying to do this on a small budget as a passion project, but the appeal of the app makes me want to complete it and launch.

Layman’s terms: My app is like a Resort-Pass tool to find certain venues (use “gyms with kettlebells” as an example). A niche tool for travelers. Replit and I built listings, with a “Directions” button, and a “Nearby” button. Somehow, the app is sending coordinates no matter if it uses Google API or Open Cage, or Foursquare to Apple Maps (not an exact address) and therefore most of the directions to each venue are incorrect by 1-3 miles.

Replit explanation:
I need help with a location-data problem that Replit Agent has not resolved.

The Agent built my iPhone gym-finder app around stored coordinates for 524 venue listings without adequately verifying those locations or establishing a reliable process for maintaining them. Data-source licensing and storage requirements also were not settled upfront. (Keep in mind that I want to eventually expand the listings throughout North American if the app is successful).

It seems Google API results have storage and cache restrictions that could drive up unexpected costs in a short time. We removed all pool pics and created original art to move away from the licensing issues.

However, location are a problem - Some coordinates are incorrect or unverified. Those same coordinates drive Apple Maps directions, “Near Me,” and straight-line distances. Consequently, a correct displayed address can still produce the wrong destination. We have not established that Apple Maps itself is malfunctioning, and changing only the Directions link would leave the other two features unresolved.

We have explored:

  • Geocodio: reviewed 25 results; some were useful, but others matched the wrong property despite high scores.
  • OpenCage: ran 32 requests across 10 venues. Its human support team subsequently confirmed that its coverage is insufficient and paid plans return the same data.
  • Google Places: potentially useful, but directory-use, coordinate-storage, and Apple Maps restrictions remain unresolved. No location trial was run.
  • Foursquare open data: evaluation was blocked by access and terms questions.

One individual correction was verified successfully (one that I did manually which is local to my home), but the Agent has not delivered a complete, verified, affordable repair process for the existing catalog and future additions. It has suggested an external geospatial developer, which I am reluctant to pay for after the time and money already spent.

Could you help arrange a technical assessment of a workable solution within Replit?

Thank you

2

I’ve worked quite a bit with Replit and its Agent, and I think you’re probably closer to solving this than you realize.

From your description, I don’t think Apple Maps is necessarily the problem. It sounds like the app has incorrect coordinates stored in its database, and those coordinates are being reused for directions, nearby searches, and distance calculations.

I’d approach this a little differently:

  1. Stop switching API providers for now. You need to determine why the coordinates are wrong before spending more money on another service.

  2. Have Replit Agent audit the location database and the code that generates coordinates. Find out where each coordinate originally came from and whether the app is actually using the correct address.

  3. Test Apple’s own MapKit location search. Since this is an iPhone app using Apple Maps, I’d investigate whether Apple’s native location services can handle more of this without introducing another provider.

  4. Build a simple location verification screen. Show each venue on a map, allow you to correct its pin manually, and save that verified location. With only 524 listings, this is manageable, especially if you prioritize questionable results.

  5. Make the app use one verified location record for directions, nearby searches, and distance calculations. You don’t want three different features producing three different answers.

Most importantly, don’t ask Replit Agent to just “fix the location problem.” Give it one specific task at a time, inspect what it changes, and test the results before moving forward. I’ve found that AI agents can get stuck in loops when they’re repeatedly asked to solve a broad problem without identifying the underlying cause.

You should also verify the licensing terms of whichever provider you ultimately use, particularly if you’re planning to store coordinates permanently.

I wouldn’t give up on Replit or start spending thousands on outside development just yet. This sounds like something that could be addressed with a better data-validation process and some targeted changes to the existing app.

3

THANK YOU. You are not going to believe this but I talked this through with a local small biz owner who has built several Replit designed apps … he gave me advice on how to approach the agent differently, switch into Pro mode, and guess what…

I spent the past 3 hours going through exactly what you described with it. It seems we now have a repair plan. The stored coordinates were incorrect!

This has been 3 weeks of frustration. But what’s weird is that I was doing all of this and then got done and saw your post which is the first bright light!

I owe you! Not much to offer right now, but this is exactly the kind of answer I needed (also to boost my confidence in the Replit Agent unless of course that’s you LOL!!!).

1 Like
4

Ok, here we go. Last night I thought we had a solution and we repaired a few listings. Now, I feel like we are stuck in a loop again. The Replit Agent, working on Pro and MAX, was planning to test another small group of the listings. I asked it to summarize what the problem is now because it keeps brining in storage.

Here is the reply: The repair works. My remaining uncertainty is about permission to reuse the source’s coordinates—not whether the app can use them correctly. I let that uncertainty dominate the discussion more than it should have.

For your developer:

  • Proven repair: Correcting a listing’s saved coordinates fixes its Directions destination. Directions, Nearby, and proximity calculations use the same database record. Three hotel corrections passed installed-iPhone checks without an app rebuild.
  • Census question: Its underlying federal geographic data can be reproduced. What I haven’t conclusively established is whether Census’s separate API acknowledgment wording applies to coordinates obtained through its Geocoder and stored in our catalog.
  • Geocodio question: Its contract permits permanent storage and reuse, but makes us responsible for any underlying-source licensing and attribution. We need to establish the applicable requirements—not assume every result has identical conditions.
  • Accuracy: Neither provider guarantees the correct property or entrance. That is why we verify candidates before saving them.
  • Cost: Lookups can happen only during catalog preparation. Customers browsing those stored listings need not trigger paid lookups. Hosting and image-delivery costs remain separate.

Popularity is not the unresolved obstacle here. Even substantial growth need not multiply geocoding charges with this approach.

The narrow question for the developer is: Which source permits this permanently stored, shared venue catalog, and what acknowledgment—if any—is required? We need that practical determination, not another broad investigation or a perfect, risk-free provider."

Any help is greatly appreciated. I really need to break through on this; I know other apps offer directions or nearby functions, but I will strip them out if I have to (reluctantly).