Manifest version number with more than 11 digits makes manifest invalid

Issue Description:
When trying to set the current timestamp as fourth digit of the version, the manifest becomes invalid.
We try to add the current MS timestamp to development builds to ensure it always has a higher version than the build before, without having to keep track of the last used number.

try 1.0.0.623768789222 as version to reproduce.
16237687892 (11 characters) works

Would be cool if this is easy to fix :slight_smile:
Impact for my app: low

Workaround: cut off the MS part and only go with seconds or even minutes

Hi, and thanks for the feedback.

We will check the issue and we will update you here.

Thanks.

Hey @Colorfulstan,

As it’s a rare case, we decided to focus on different requests. So, unfortunately, we will have to reject it.
We encourage you to keep suggesting ideas!

Thanks.