Messages

Apologies for jumping in on this conversation, but it is of some interest to me.  I was very confused as I did not have the "Tap and Hold to Display Address" setting enabled, but I got it now and can see the reasoning. Hope this helps (and is correct !)

The issue, I think, is whether or not you have got the offline Lomaps for your region downloaded, even if using a different map.  When creating a point in a route this is where it gets the address data from. I don't believe OAM maps include the address data. If that Lomaps address data has not been downloaded then you get just "Shaping point" or "Via Point" in the point's name.

However (provided setting "Controlling/Map Screen/Tap and Hold to Display Address" is enabled !!) when long pressing on the map it DOES show the address - so it must be getting this online - I proved it by setting Airplane Mode - and it can't then get the address.
But when adding the point it still uses the offline Lomap as the source, so this does seem strange/inconsistent. If the offline data isn't available then why not use the online as it has already got it ?  Maybe there is a technical difficulty with that.

For myself, I do have the offline Lomap downloaded for my region so everything works fine. As long as you don't mind the extra storage space needed, that is one solution to the missing address in the point.

On the question of Shaping versus Viapoints.... position cursor at the location, long press on the "+" button at bottom left, then choose "screen centre" will create a viapoint with name filled in with the address. Alternatively there is an option in the route planner settings "Via points as default".  You might want to try that out.  But I suggest download the offline Lomap first.

I can't see a way to directly edit either a Shaping or Viapoints name/icon data. Seems you can only do that when changing from Shaping to Via Point.
So to change a Shaping Points name (or icon) change it to viapoint, edit, then back again, To change viapoints name, change it to shaping point, then back to viapoint then edit.
Could be improved I think, unless there is some other way of doing it already but I can't see it.

Haven't seen anything about app factory problems in Android 14 but I dont use myself so don't know. Have you tried the obvious things like rebooting and/or recreating the app ? 
However, if stuck then you could try these alternatives.

1/ Install Locus/Tasker plugin.
Run plugin app; Settings;   Ensure "Run Task From Functions" enabled. Set Regex to match just your tasker task. (format "Projectname/Taskname"  - Default Project is named "Base")
Locus: configure menu; Add Function - add "Run task" from "Add-ons" section.
One tap needed to run, provided Regex matches just one task else it shows a selection list.

2/ Quick BookMark
URL    tasker://assistantactions?task=YourTaskName&par1=YourValue1&par2=YourValue2
Two taps needed to run.

3/ Tasker secondary app.
Tasker: Preferences/ActionTab - ensure "Secondary App Enabled" set. Create profile using "Secondary App Opened" event and map to your task.
Locus: configure menu; Add app - Tasker Secondary.   
One tap needed to run.

There might well be other ways. (e.g if Locus can trigger app shortcuts or send user defined Intents then Tasker can react to those and map to Tasker task)

Hi
I only just noticed this item. 
I have to plead guilty to using the plug-in "map_center_altitude"  but only in one tasker task and only when testing it - which clearly I haven't needed to do for some time (since originally writing it) as I had not noticed it now returns zero.
I suppose ideally it could be enabled only when needed - e.g only if GPS disabled, or perhaps an expert setting, however if that is too much effort then fine.

(BTW I do use map_center_lat and map_center_lon in several tasks and much more often)

If you don't mind not seeing real-time display of point on map, then you could probably do this using tasker and save the points data to a file, then import to Locus at home, or periodically when convenient when on road.

(ie. detect key strokes in tasker (various ways of doing this) with different key/letter (or combination) for each point type,  get lat/lon via locus/tasker plug in or from tasker itself(slower), then write/append gpx format waypoint line to file, alert (e.g. beep) on success/fail).

On the other hand...   "finalize support for so-called Actions Tasks"  .....  Yes Please!!   
e.g. QNP, export currently navigated route, import/export track or points, 'navigate to' with auto start nav, Nearest Point when navigating,  etc        
Currently have to use tasker Autoinput (screenscraper) which is far from ideal.