PKraenzlin011926 (Community Member) asked a question.

DevOps 'Veracode Upload and Scan' - Upload stops when file name contains 'umlaut' like 'ö'

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:

  1. Starting: Veracode: upload and scan assemblies ..
  2. ..
  3. Start Obtaining App Info
  4. ..
  5. End Obtaining App Info
  6. Start Obtaining Sandbox Info
  7. ..
  8. End Obtaining Sandbox Info
  9. Obtaining Build ID of Last Build
  10. Start Obtaining Build Info
  11. ..
  12. File Upload-Scan Task Started
  13. Uploading: drive\folder\file1.exe
  14. Uploading: drive\folder\file2.dll
  15. Uploading: drive\folder\file3.dll
  16. and - so - on ...
  17. Uploading: drive\folder\fileÖ1.exe
  18. <!!HERE!! - There are more files, but they are not uploaded>
  19. Start Obtaining Build Info
  20. ..
  21. Start obtaining region details
  22. ..
  23. End Obtaining Build Info
  24. Start Obtaining Build Info
  25. ..
  26. Start obtaining region details
  27. ..
  28. 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.

 

 


  • 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:

    1. Navigate to the upper right corner of any page in the Community, click on your user avatar.
    2. Select Contact Support from the drop-down menu.

     

    Jason

    Veracode Support Engineer

    Expand Post
  • PKraenzlin011926 (Community Member)

    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!

    Expand Post

Topics (1)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.