The Package XXXXX failed to save.

Putting this here to add to the list:  Upgraded to 10.35 last night, tried uploading a .dmg and also getting "The package "***" cant be saved." Cannot see the package in JAMF Admin, however when I try a second time to upload it asks me to replace the package. Rolled back to 10.34.2 JAMF Admin and was able to upload successfully.

same issues here

Same issue here. Updated PROD environment on Friday

Same here; except using 10.34.2 as a workaround doesn't work for uploading packages either. 

Having the same issue with 10.35. Trying 10.34.2 and will report back in a few.

Worked like a dang charm! lol

I also had to revert to an earlier version of Jamf Admin as this started happening to me as well.   We use the cloud version of Pro if that matters.

Has there been a solution to this that doesn't involve downgrading?

Just upgraded my on prem and got caught out by this issue. I am noticing it seems to be taking a lot longer to mount the distribution point. I am on Monterey, and my server and repository in on a Windows Server 2012 r2 with repo on the same server.

While we haven't updated our server to 10.36.0 yet, we see the same error with that version of Jamf Admin on a 10.35.0 server. 

I'm still getting this same error on 10.36 and have to downgrade to 10.34 for packages to upload successfully. Is there some other workaround or a bug fix for this, or something on the MacOS settings I'm not seeing? Just curious what's actually causing this error.

Search fo Jamf Admin here:

https://account.jamf.com/products/jamf-pro/known-issues

It looks like they cataloged it as a bug. 

"New packages fail to upload in Jamf Admin 10.35.0 or later. Workaround: Upload new packages using Jamf Admin 10.34.x with Jamf Pro 10.35.0 or later."

Thanks for the heads up! We'll just have to run the earlier version for now. 

I also seen the same issue on 10.36 just released.  Hopefully Jamf actually read this. 

same here. Just updated to 10.36 and couldn't get a simple package to work. Installed the 10.34.2 and it even accepted the package that was already on the DP. Saved it after adding category and indexing. Tested the install as well without any issues.

It has to be something wrong with 10.35.  I was having the same problem.  I was uploading a macOS Monterey DMG file and getting the same exact error.  I didn't make any account/permissions changes.  I just moved the DMG file over to another workstation with 10.34 installed.  I opened Jamf Admin, I got no errors and wouldn't you know it; there was my file.  I made my changes and clicked save with no errors and it showed up in my packages in Jamf Pro.

Rumor has it that 10.37 has the fix. 

This would have been nice to know before having to troubleshoot it for 2 hours.  

We have the same issue.

10.36.1 here. Using 10.34.2 worked for me as well. Looks like the issue is still present. 

What about 10.37?

Ive just installed 10.37, can confirm issue is fixed in this release.

Same here. Incidentally, they also changed the download options to download only the Jamf Pro apps. 

Edit: I spoke too soon. Looks like I am having the same issue. Any one else?

I am also having this issue with 10.37. I was able to use 10.34.2 and uploaded the .pkg fine. We also have a local Windows SMB share for our DP.

Anyone know whether this is fixed in v10.39.0?

I have used Jamf Admin 10.39.0 and Composer 10.39.0 a few times this week and not had any issues with either.