Find My apps on new Ver

This usually happens when location sharing permissions are mismatched between you and your contacts. Since they can see your location but you can’t see theirs, it means your side of the connection is fine, but theirs hasn’t been fully enabled. 

Network & Privacy Settings

• Both devices need a stable internet connection.
• On their phone: Settings → Privacy & Security → Location Services → Find My should be set to While Using the App.
• If Location Services are off, you won’t see them.

The process shown in the image must be enabled on both devices.

To use Find My and Location Services on an iPhone effectively, both your iPhone and the device you're trying to locate must have an active internet connection. These services rely on internet access to share your location with friends and family and to track the locations of devices, people, and items. Without internet connectivity on either end, the sharing and locating features of Find My and Location Services will not function properly. --> Internet not available WiFi and Cellular … - Apple Community

Useemehere2 wrote:

I think the new Ver. 27 has a glitch regarding this Find my app

Not every issue an individual encounters on their device can be attributed to an iOS update. iOS 27 or later may have coincided with what you are experiencing, but that does not mean the issue was triggered by iOS. Coincidence in timing is not, by itself, evidence of causation.

If the update itself were the root cause, then every device running that same version of iOS would exhibit the identical problem. In such a scenario, the forums would be flooded with countless posts reporting the same malfunction, creating an unmistakable wave of complaints that no one could possibly overlook.

The absence of such widespread reports strongly indicates that the issue is not a general, system-wide problem with iOS 27 or later, but rather something specific to the individual device, its configuration, installed apps, settings, hardware, or another interacting factor.

In short: iOS 27 or later may be a coincidence in timing, but there is no basis to conclude that iOS itself triggered the problem simply because the issue appeared after the update.

See what each update does: About iOS 27 Updates, About iOS 26 Updates, About iOS 18 Updates, About iOS 17 Updates, About iOS 16 Updates, About iOS 15 Updates, About iOS 14 Updates, About iOS 13 Updates, About iOS 12 Updates, and so on...