
PKraenzlin011926 (Community Member) asked a question.
Hi there
I didn't knew where to place the issue question, so I selected 'community' ...
We use the DevOps 'Veracode Upload and Scan' extension and encountered the following situation: The file upload starts but stops at the first assembly which has a 'ö' character inside the file name.
The log basically looks like this:
- Starting: Veracode: upload and scan assemblies ..
- ..
- Start Obtaining App Info
- ..
- End Obtaining App Info
- Start Obtaining Sandbox Info
- ..
- End Obtaining Sandbox Info
- Obtaining Build ID of Last Build
- Start Obtaining Build Info
- ..
- File Upload-Scan Task Started
- Uploading: drive\folder\file1.exe
- Uploading: drive\folder\file2.dll
- Uploading: drive\folder\file3.dll
- and - so - on ...
- Uploading: drive\folder\fileÖ1.exe
- <!!HERE!! - There are more files, but they are not uploaded>
- Start Obtaining Build Info
- ..
- Start obtaining region details
- ..
- End Obtaining Build Info
- Start Obtaining Build Info
- ..
- Start obtaining region details
- ..
- Finishing: Veracode: upload and scan assemblies ...
At mark '18', the file upload stops, even there are more files to upload.
If we exclude the certain files, the file upload works well and takes also files after the 'ö'-indexed ones
So: Is this a bug or a known limitation?
Thanks for your replies.
.png)
Hello @PKraenzlin011926 (Community Member) ,
Engineering has confirmed the information in the Help Center article Understanding Veracode General Packaging Guidance, states that umlaut is not a valid UTF-8 character and what is causing that issue to occur. Please make the necessary changes and try the upload and scan again.
If continue to have problems then open a Support ticket. Here's how you can log a case:
Jason
Veracode Support Engineer
Hi Jason
Thanks for confirming our guess. Actually 'ö' (as any other umlaut) is a valid and printable character according to UTF-8, but I rather guess, the file upload accepts only ANSI 128 characters (which do not include umlauts). Maybe, you can forward this information to the engineering or update the documentation.
But for us it's fine, we will change the file names accordingly ...
Thanks again!