Join our newly restarted iOS Beta and try out new features sooner: https://testflight.apple.com/join/PDzBYbJw
Read more about ABRP beta at Installing the ABRP Beta version
From the last updates ABRP became unusable. Planification is correct but it is impossible to start navigation. The road becomes « undrivable « See the screen copy
Road is visibly broken northbound at lat/long 34.93999, -113.66437. Been this way for at least six months despite OSM fixing the issue upstream after some construction there for highway expansion. ABRP refuses to route through it (instead using routes that take 1-2 hours longer) even with many guidepoints placed every few feet through the problem area- it simply thinks the road is disconnected or no access there, with no alternatives besides turning around and driving an extra 200+ miles to get around a broken 20 feet. Road is currently open with no restrictions. Seems to also have been reported (with less detail given) at https://abrp.featurebase.app/p/erroneous-closure-info-for-us-93-destroying-routing-from-phoenix all the way back in April. This still not being fixed for this long is seriously making me reconsider my subscription- it's the main route I even sub for.
My EnBW "L" rate isn't showing up in the plan. My price is €0.39, not €0.60.
Yesterday, the GPS took me to two addresses via the wrong routes, directing me to make illegal turns 🚫, and I almost got a ticket because of it. I went back to using Waze, which has never put me in that situation, and tried to cancel my subscription, but I couldn't find the option.
Just like Maps/Waze or the Dutch Flitsmeister. Now it even states there is an average speed enforcement on quite a few roads where there are now speeding cameras
The list is missing byd sealion 7 premium rwd. Requesting if this vehicle can be added.
Not routes from my home. From Las Vegas to Ely NV, for example
Hi everyone, I’m an Annual Premium subscriber. Until October 14, the app was compiling daily history normally—combining each entry into a single record—and I was able to review the data related to my daily trips that way, but starting on October 15,something happened (I assume) due to a software glitch, because the routes—which had been recorded perfectly well up until then and were easy to follow afterward—have been recording jumbled data since the 15th, showing 30, 45, or 50 for a pre-programmed route of, say, 10 km. I’m attaching a screenshot of the error. What could be the problem?
Je voudrais ajouter le Peugeot e2008 2023+, avec une batterie de 50kwh et un moteur de 136ch
I’m planing a drive for December, spanning 4 days. I can set the departure date and time, but if I edit the same start point a while later, or after I reload the trip from saved trips, only the time is stored. The date reverts to today. The white outline indicator for which properties has been manually selected disappears from both the date and the time fields, but the time is still correct. The time below is set to 08.00, but the date should have been 18.12.2026, not 18.10.2026. I also have a single charging location, where I adjusted the kW and target. When the settings for the stop is open, the two fields are highligted, but in the route plan, the settings button is not blue like the others. This it similar to the https://abrp.featurebase.app/da/p/routing-date-error-cannot-plan-future-trips which was solved back in June, but must be a regression, since it still happens for new plans.
I would like to see altitude information on the carplay app screen or in the form of a widget. Time on the x axis, soc and altitude on the y axis, just like the graph on the phone app under the drive history menu. Thank you