Drone ID not getting GCS GPS fix from TCP Client

Updated our copter to run the Beta firmware to implement Drone ID. Running a TCP client on my phone with NMEA protocol GPS signals. Verified connection from Mission Planner as well as a python script that makes sure the GPS signals are active. Here is the format my phone is sending to MP:



However, Mission Planner says “Connected to TCP14551. Waiting for fix” and never locks onto this signal. Is it an issue with the app I am using (GPS2IP on IOS) or format of the NMEA string? Thanks for any help!

Just wanted to see if anyone has found a fix for this. I know this is a new feature and is rapidly changing, just not sure what to do as RemoteID won’t enable with our gps running and connected.