SOTI Pulse Logo

packages/V2 API : limitation on PackageVersion

LR
Laurent Riffard
EHTRACE SAS

Hello,

Using API packages/V2 works fine but setting "PackageVersion" in payload seems to have limitations in naming. Some like 2.3.0-SNAPSHOT-1, 2.3.0S123456, 2.3.123456789012 fails with same error:

{ "$type": "ErrorDetails", "ErrorCode": 0, "Message": "Impossible de créer un nouveau package.", "Data": [ "La version du paquet contient des caractères non valides." ], "HelpLink": null }

On console, when uploading a pcg built with name like 2.3.0-SNAPSHOT-1, it works fine and name is ok. 

Why this limitation ? Could it be removed ?

And, what is the rule for naming? a regex ?

Thanks for your help 

2 years ago
Android
ANSWERS
RS
Rafael Schäfer
2 years ago

But the error message is not complaining about the file name but about the version number inside of the package to be invalid.

The package version contains invalid characters.

Did you try to upload exactly the same package via console (with the same version number set)? I would expect it will fail as well.

LR
Laurent Riffard
2 years ago

Hello,

You're right, when I was talking about "name like 2.3.0-SNAPSHOT-1", I mean version. I confirm that all my issue come with PackageVersion.

When I upload via console a pcg built with package studio, it works fine and this version is fine. Now I'm trying via the API, it fails

Here are all the manual upload previously succeed:

RS
Rafael Schäfer
2 years ago

Do you upload the data in the request like this (only for apps!):

{ "DeviceFamily" : "AndroidPlus", "PackageName": "package", "PackageVersion": "1.0"}

or this (packages):

{ "DeviceFamily" : "AndroidPlus" }

 
LR
Laurent Riffard
2 years ago

This way:

{"PackageName":"myPackage", "PackageVersion":"${version}", "PackagePlatform":"Android",
"ScriptFiles": [{ "FileName":"${postInstallFileName}", "ScriptTrigger":"PostInstall", "FileSourceType":"Binary" }],
"PackageFiles": [{ "FileName":"${f.name}", "FileSourceType":"Binary" } ]} where ${version} is the one that makes me crazy

RS
Rafael Schäfer
2 years ago

Ah sorry, i wasn't looking into V2.

But did you try other way around, for an uploaded profile where your version string is like the one issuing?
Just to see if it maybe expects something different when uploaded and compare it with the data you upload.

RC
Raymond Chan Diamond Contributor
2 years ago

I haven't tested out your reported API to see if I can repeat your problem, but I wouldn't be surprised that there are unexpected naming restrictions (or parsing error), as similar issues happen from time to time for different MobiControl new objects/scripts/API etc. in different versions of MobiControl over the years.

If you or your company is a registered user/customer of Soti MobiControl, I recommend you to send an e-mail with sufficient details (test results, screenshots, etc.) directly to support@soti.net to open an official support case with a well-defined support case number.   Once the problem is confirmed,  there might be update in documentations on the naming restriction or plan for working on parser fix(es) in future patches of MobiControl.    If you only voice out problem in here,  I don't think any forum facilitator will open any support case for you, nor will there be any other solid action taken to follow up or fix the problem.  

M
MPMOD@SOTI
2 years ago

Hi Laurent,

Thank you for posting on SOTI Pulse! 

Please open up a case with technical support, as Raymond eloquently suggested. 😀

I would like you to create a support case (click here) or call the SOTI Support team (click here) to raise a New Case so that our team can look into this further for you.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net lDiscussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter

LR
Laurent Riffard
2 years ago

Hi,

Actually, I've already sent an email last thursday to support, following Raymond's advice (Case: C00670130)

Thanks

M
MPMOD@SOTI
2 years ago

Similar Discussions