error:failed when trying to export as apk, array task broken now.

It fails in Tasker itself. What I'm doing is creating two arrays, then merging them. What ends up happening when it fails is that the second array becomes about 10X bigger than it should and so the Merge Array then fails because both arrays have different amounts. Right now I'm iterating through the different versions of tasker from 6.2.7-beta to see which one it started to fail in.

Can you please export a minimal example of that as an URI (not a link, but a direct URI) and paste it here so I can then import it and test it myself?

Thanks in advance!

Sure. Also I have traced the failure to far back to some build of 6.2.14, and I'm iterating through them now. It fails on task #13 ends up giving me a "Error: null", whereas the versions before that work as expect. Here is the Data URI

Also that references another task "Progress Bar", which you can just delete those for the sake of this since it's obviously not needed to troubleshoot this.

Ok I FOUND IT!! I found which exact version of Tasker this broke on. It's version:

6.2.14-rc-20230926_1120
The one right before this worked no problem, which was 6.2.14-rc-20230926_0923.

Thanks! I tried it out but, just after deleting all the references to the Progress Bar task, I ran it and only got an error in the Arrays Merge action:

10.47.53/E All arrays must be the same size. %LabelsForSettings has 20 elements while %GetPropSettings has 413 elements

This is not the same error you're getting, right?

Would you be able to create a small test task where you just use hard-coded values (and not values that depend on each system) where you can demonstrate the error?

That way it will be way easier for me to replicate it :)

Thank you very much!

So that array error is the same one I was ORIGINALLY seeing at first, but now I'm getting the error on the RUN SHELL action which runs:
echo $(echo "%app_name()" | sed 's/[^a-zA-Z0-9 ]//g');

and saves the output to %SettingsInput

If I put a checkmark in "Continue Task After Error" it then gives me that same error you are getting now. However, it originally was giving me this error without me doing that.
I'm not sure what you're asking me to do, so I don't know how to help you troubleshoot this other than me just sending you the task like I did. Would it help you if I did something like logged this in Tasker to see what happens in the version that it's broken on vs the version it works on?

So, what would help me figure this out is if you made a task where you didn't get any values from the system, but instead had some "Variable Set" actions that set some variables to the exact values that produce the array error you mention on your device.

For example, instead of using the List Apps action to set the initial %pkg variable, which will be different for each device, set the %pkg variable manually with the actual value you get on your device.

If you do that for every variable in the task (write the value directly instead of getting it from the system) I can take the task and run with the exact same values as you would and then get the exact same error so hopefully I can fix it, because I can reproduce your exact situation :)

Let me know if this is clearer.

Ok so this is what I found, if I change "%pkg(+/)" in the "App Info" action, to "com.android.chrome", and just select "Chrome" since that is the only option that then comes up, the task runs succesfully. HOWEVER, with keeping "%pkg(+/)" as it is, but selecting "Chrome", it fails for me at action "Run Shell" with the command "echo $(echo "%app_name()" | sed 's/[^a-zA-Z0-9 ]//g')" with "Error:null" as you can see here:
https://imgur.com/jlTH5Tb
This happens as SOON as I switch to Tasker version 6.2.14-rc-20230926_1120. The previous versions I did not get this error and this task completed as expected.

Was that what you were asking me to do?

Yes, something like that :)

Can you please try adding a Flash action before the App Info action with the text %pkg(+/) and see what it shows?

Also, can you please

- enable the Continue Task After Error option in the Run Shell action

- set the Store Errors In variable to %shell_errors

- add a Flash action action after the Run Shell action with the text %shell_errors

What does that show when you get the error?

Thanks again

Ok! This is the error for %shell_errors:
sh: <stdin>[3]: no closing quote

Weird. With version 6.2.14-rc-20230926_0923 and before, it's fine. As soon as I update to version 6.2.14-rc-20230926_1120 it gets that error. Even on the latest beta 6.3.0 it gives the same error. Also the popup of %pkg(+/) shows the same thing whether it works or not, it shows the installed packages separated by "/".

Ok so I just tried changing the double quotes to single quotes in that shell command and then that action completed without errors then when it gets to the Arrays Merge action, it fails, it says that one array has 20 elements and the other array has 639 elements. This fails start on version Tasker-6.2.14-rc-20230926_1120, and then also I tried it on 6.3.0-beta. It fails the exact same way on both of those.
However, it functions successfully with either double quotes or single quotes on version Tasker-6.2.14-rc-20230926_0923.

Ok a few more things I tried to see what was going on and the Array that is getting too big, is %GetPropSettings(). I made a popup action to show it to see what was going on. Here it is when it is working, this is what it looks like:
https://imgur.com/JhQUIFF
And when it fails, this is what it looks like:
https://imgur.com/cSDEm1f
It appears the Array is being processed entirely differently in the versions of Tasker where it is getting too big.
I hope you are able to reproduce this on your device.

Thanks! Can you please check what the %appname() array contains after the App Info action in both cases?

I think a change in the App Info action may be the cause of this!

Thanks for your help!

%app_name() and %app_package() look identical between the working version and non-working version. I have output them to text files if you want but they are identical.

Ok so I've been doing a bit more digging. Here's how this task works when it does work on the versions it works on:
%GetPropSettings() is supposed to only contain the name of the selected app, and it's package name, then results of a query for the current device settings of certain "setprop" values. For example, when it's working, it returns something like this:
https://pastebin.com/DFuJQ0CD

Now in the versions of tasker that it's failing it's getting ALL of the names of the installed apps AND their package names. It should ONLY contain the name of the app selected and that apps pacakge name, but it contains EVERYTHING, the names of every single installed app and their corresponding package name. You can see here:
https://pastebin.com/bsVqesMX

This issue SHOULD be device agnostic, so I suspect you should be able to see this exact issue on yours when running it.

OK So I found EXACTLY where this is breaking. It is breaking on the results of the shell command:
echo $(echo '%app_name()' | sed 's/[^a-zA-Z0-9 ]//g');

The results are supposed to be stored in the variable %SettingsInput. The purpose of this is to "sanitize" the app name from any characters that cannot be written to a file or folder name, as some apps had characters in their names that when trying to write to a file or folder with the app name, it would fail, hence the need to "sanitize" and remove these characters that cannot be written to a file or folder name. Here are the results of the task when it has finished correct, I output the arrays and variables to a text file, you can see the results here and they are correct:
https://pastebin.com/pXxsvk55

When it fails, it fails on the variable "%SettingsInput". Instead of only containing the name of the selected app, it contains the names of EVERY SINGLE INSTALLED APPLICATION, and this breaks the task. You can see the results here:
https://pastebin.com/5RyDwjkH

Here is an updated DATA URI of the task for testing:

****I FOUND THE SOLUTION****

So changing %app_name() to %app_name in the shell command fixed that output issue. 
Also I had to change %app_package() to %app_package in the other shell command.
So I guess you are correct, this has something to do with a change in the App Info action? Was it broken before and you fixed it now and I was just using a work-around, or is it broken now from how it should be and I just discovered a work-around? Please let me know. Because if this is how it will say I'll just make sure any other actions I have will reflect the current processing of App Info! Thanks, hope to hear back from you soon.

Ah yes, it was broken and now it's fixed 😅 Sorry for not remembering earlier! Glad you found it!!