Animate Appending/ Editing "Output Name" until Character Limit is exceeded

[Juniperf]

This only appears to be an issue with some specific HTML5 Canvases of mine. Starting a new file does not replicate the issue. 

In a new file, it's easy to click the Publish Settings button, type or select a path, then publish. 

In my working files, each time I try to edit the path, Animate appends a dozens ".../.../.../" to the beginning of the path. Then, I'm unable to publish because the path name exceeds the 250 character limit.

Does anyone know what's going on here? I've tried different (shortest possible) paths, different (single character).output names, none of it working. 

[Juniperf]

This is also my first time encountering the character limit issue in the first place. While I don't see this becoming a problem for myself in non-buggy scenarios, I'm curious as to why it exists in the first place and what purpose it serves.

HTML5 Canvasses are used so much for online creative that Animate labels their section as "Ads." A single ad campaign can have many groups, timings, sizes, and variations. Nested folders is not only good practice but essential to staying organized when working with hundreds of files and thousands of assets across multiple campaigns each year.

Beyond that, collaboration is so important nowadays that many large companies rely on cloud services so that employees can easily share work between locations. Cloud storage is always going to lengthen the path name, sometimes by a significant amount.

[kglad]

use file-safe naming that utilizes an initial alphabetical character and thereafter alphanumerical characters or underscore and save to a directory that follows the same protocol.

[Juniperf]

I've tried that. For example, naming the file "a" to a folder on my desktop also called "a"

[kglad]

sheesh.  at least, use different names for the folder and file.

does the problem occur with a new fla?

[Juniperf]

That's uncharitable. Normally, the files and folders are named based on conventions set by my team.

Despite the fact that the files / folders sharing a name shouldn't matter, the example I gave you was that - an example of one of the many tests.

As I said in the post, in a new fla file, the issue is not able to be replicated. 

[kglad]

you're correct. that was unkind.  i apologize. 

can you upload the problematic fla to a file server (eg, dropbox or wetransfer etc) and post a link?

[nataly_cocoon]

same issue... any solutions?
ta

[SofieKatan]

I had a similar issue. 
It was fixed by saving the fla file as a new file and then setting the directory for the publication again. 

[kglad]

@SofieKatan 

thanks fir the confirmation.

[nataly_cocoon]

I figured out my problem. The AI file and everything else were on Google Drive and the path was too long I guess. I also saved it in a new location (directly on my computer) and it worked. 

[kglad]

for others, again:

use file-safe naming that utilizes an initial alphabetical character and thereafter alphanumerical characters or underscore and save to a directory that follows the same protocol.