tl;dr version: How do I get a route from Ride with GPS into an iGPSport iGS630S?

I'm accustomed to Ride with GPS (RwGPS): I routinely use it on my computer when I'm at home and on my phone (in my back pocket) while on rides.

After major procrastination, I bought an iGPSport iGS630S. I installed the company's "app" on my phone (running Android MIUI Global 14.0.4), and successfully paired the head unit and the phone.

The page "Me" in the iGS630S's "app" has the option "Link Other Apps"; but the three possibilities (Strava, Training Peaks, and Komoot) don't include RwGPS.

I got RwGPS (on my computer) to export a simple route as a .gpx file (with no "points of interest" or "cues") and mailed it to my phone. (It's only 181kiB; so no problem of size.) "Downloaded successfully", said the phone, which offered to let me "Open with" any of several apps; and yes, "iGPSPORT Ride" was among these, so I clicked on that.

iGPSPORT Ride responded "Non-GPX file is not supported."

The way I made the .gpx file in RwGPS is the way I sometimes make one for friends who use alternatives to RwGPS.

What stupid mistake am I making? (I mean, other than not buying a different head unit, not using Komoot....)

Did you export the file from RWGPS as a GPX Track or GPX Route? If the latter, that may be the problem. The GPX Track format should be standard and compatible with most, if not all, GPS units.

According to the manual, "The files in GPX format can be directly imported into the iGPSPORT APP as the navigation route." so it 'should' work.

Thank you, Aushiker! But I'd used "GPX track".

I tried getting a "GPX track" from the same RwGPS route for a second time, but this time taking the option to "Reduce to 500 points". The resulting file was only 11.6 kiB. The iGPSport software was happy with that.

I wondered if the iGPSport software might just be flaky, sometimes recognizing .gpx files and sometimes not. So I tried feeding it an entirely different "track" (this time 500 kiB: thus a lot bigger, but still not what I'd call big). Nope: "Non-GPX file is not supported."

Ah-ha! I think I have it. This page of somebody's blog is very informative and well written. (It's in Japanese, but Google Translate does a good job with it.) Simply, I'd been attempting to push the .gpx file into the app; but one should instead go into the app and pull the .gpx file into it. And sure enough, that worked.

No, I don't understand why doing the one brings an error message but doing the other succeeds; but then my phone is a mystery to me. Fingers crossed that I've achieved "interoperability": unfortunately I'm now paralysingly sleepy (my phone does this to me), so I'll pause this little adventure till tomorrow.

Sounds like a bug in the app. If it works one way, it should work the other way.

It does indeed seem like a bug. (A bug somewhere -- I'm always looking to assign blame elsewhere, but it's possibly in my own aged brain.)

I have to rush off for a ride, so I'll return to the matter several hours from now.

'That is interesting indeed. At least it works.

Sorry for the late response, but I had to leave home early yesterday to join a ride; and I returned home exhausted and sweaty. Body and brain have now partly recovered, and so I'm ready to experiment. The phone got my .gpx file into the device, and the device shows that yes it has the .gpx file. I don't know how to display the .gpx file, but maybe that's because there's no signal where I am, indoors. And I'm indoors because (i) it's bucketing down outdoors and (ii) I'm a wimp. The bike's going in for servicing later today (and I shall get thoroughly wet), and I'll get it back on Monday. First priority: turning off the noisy beeping!

I wonder how long it will take me to remember the functions of all six of the buttons on this device. Oh well, this system perhaps beats that of a touchscreen non-operated by sweaty fingers and operated by raindrops.