Upgraded to V 12, route calculation stops at 39% and crashes device

Update, same routes worked fine with version 11.2 

Why did Garmin release this when fully aware of crashes in Beta testing … Garmin Software development and test never ceases to amaze me.

I checked the now prepared course with RWGPS 92km - the route marked with a pin, automatically synchronized with Connect, sending to Edge 1030, after synchronization it was easily converted by Edge.
Why are you using the old IQ sync app? This method is abandoned and the app may cause problems - pin the course and send to Edge with connect, it should be easily verified in Connect and sent to Edge. If you (like me) have Connect segments (I transferred my favorite strava segments) then the route will be completed with all segments from this course. This applies to courses from any service such as Koomot, RWGPS, travel.cycle, or even Strava without premium!

The point is that those same routes worked fine with earlier firmware!

Where is staeted that IQ apps are abandonded?

I have noticed that if I use Garmin connect method it sometimes messes the courses (creates its own ways) 

Did you notice that also Strava routes fails, those are using API.

Thanks for sharing your way of working with routes.

Look at the app's page: apps.garmin.com/.../945c964a-314b-41fa-9a13-32a1f7931335
and Strava FAQ: support.strava.com/.../115000919304

What if I use the Strava Routes ConnectIQ app?
It is no longer supported and will be removed from the Garmin ConnectIQ app store.

and current comments:
Why isn’t this supported anymore? :(
Does not work anymore (error 402)
strava routes error code 2050 etc.

Probably the same applies to other services that have synchronization applications, and from the release of the Garmin API to course synchronization, most of these applications have been abandoned and their operation on new systems with the new CIQ may be buggy.

I just checked the 100km course from Strava. Works flawlessly. Of course, without the use of the CIQ app.
At 39%, it stopped a while longer, but soon completed a course recalculation.

I dont use IQ app with Strava, onlly that API (yuo star route and it appears at device routes)

But with RWGPS, there is no alternative for direct transfer than IQ app.

I dont want to use phone on route ( it sticks in my back pocket) , only garmin device.

I downloaded the CIQ RWGPS app and it works normally, I tested a 130 km course and it was recalculated quite quickly, it stopped for a while at 39%, but soon it completed the recalculation.

Of course you can use RWGPS with your phone. I just checked - the browser (mobile Chrome) works nicely with RWGPS in mobile mode. The pushpin is available for previously planned routes, the planner works poorly in this mode (rather unusable), you have to switch the browser to computer mode.
I have not used the RWGPS mobile application for quite a long time.

Maybe share problematic routes? I'll check with me.
Can you check if the Edge drive has no errors after connecting to a PC?

Here you have on example of failing routes

ridewithgps.com/.../36490472

I checked:
RWGPS CIQ application: Error loading route. I checked several times, maybe there is a problem with the CIQ application sharing (private route? set to public, I'll check again), because I download my courses from the CIQ application without any problems.
Pinned and downloaded via Connect - coruse recalculated without any problems. A bit long, but there was no problem.

Hi. I have been keeping an eye on this thread and have a couple of ideas

It could maybe be an issue with the popularity routing recently added. Is it enabled or disabled on your device? If enabled try disabling it

Also It may be something to do with the edge thinking that some roads are not suitable for cycling & cannot find an alternate route. This may be due to the avoidance settings in your activity profile or one of the inherent avoidances that are set by default for each activity profile, & there is no way to change those eg for the Road Cycling profile it avoids Major Highways where cycling may be prohibited, which in the US can take the form of Interstates etc, however in the UK some Major Highways are legitimate roads to cycle but the edge won't use them when the Garmin maps are enabled resulting in route calculations being ridiculously long or the edge not being able to find a navigable route. So to get round this I have to use a 3rd party OSM map, where the roads have been categorised a little differently.

Another thing I found with avoidances is the 'Avoid Ferries' avoidance. Even though there aren't any ferries within 100 Miles of my location, Quite bizarrely when 'Avoid Ferries' was enabled the route calculations wouldn't use certain roads.