@doekman check for Self Service app > App Config > in the plist if the below key pair is missing:
<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>

If it's not present, add it and save. Then quit and re-open Self Service.

We have the same Problem.

I'd recommend to check the same.
Editing the app with the key pair should be all what's needed.
Upon saving, you should see MDM commands called "Settings - Managed App Configuration" starting to be sent to devices that will pull down the new config and let Self Service re-connect (needs to be quit/re-open).

Is this requirement new? The self-service app entries in my MDM only have the UDID entered and not the MANAGEMENT_ID. In the product documentation for Jamf Pro, only the MANAGEMENT_ID is entered and not the UDID.

Please refer: https://learn.jamf.com/bundle/jamf-pro-documentation-current/page/Jamf_Self_Service_for_iOS.html

Which configuration is the right one now?

The Preferences-textarea is empty. Is this a new thing, since in the past Jamf Self Service worked.

Also: because it's empty do I need to enclose the xml in a dict-tag? So like:

<dict>
<key>MANAGEMENT_ID</key>

  <string>$MANAGEMENTID</string>
</dict>

Depending on how you're deploying Self Service (Apps&Books, manual install etc), there's example plist config here: https://learn.jamf.com/bundle/jamf-pro-documentation-current/page/Jamf_Self_Service_for_iOS.html

The MANAGEMENT_ID have always been optional.
With the latest release of Self Service, it looks like it's mandatory now.

I am having the same issue with Self Sevice, it seems to be the 11.2 update of Self Service.

I was ok until it updated.

I haven't had that MANAGEMENT_ID key in my App Configuration ever and our Self Service broke with this 11.2 update. Not sure if I missed something but adding it in seems to resolve the issue.

Is this official, are there any release notes for Jamf Self Service that contain this information?

Good Morning, 

I started having the issue when the iPadOS updated to version 17.1.1.  Prior to this everything was happy.  

VickiH

This worked for my environment, thank you!

The issue is not iPadOS 17.1.1. I have iPads with earlier iPadOS versions that are having this issue this morning. The issue comes with the update to Self Service version 11.2.0. Adding the MANAGEMENT_ID key in the Self Service app configuration fixed it for me as it did for others.

Hello,
any ideas when the MANAGEMENT_ID does not solve the problem?

Did your devices receive the new updated management configuration command after you added the key? In our environment we force push Self Service so we can delete it and run an inventory update to install it again. This makes sure it has the new App Configuration settings with it.

It may have worked for you and others but it is not working for me and some others after adding the key.  The only time I started to have the issue was after I updated to 17.1.1, prior to that it was working.

Thank You

I did that as well and I'm still receiving the same message about it being a component of Jamf Pro and it must be associated with a Jamf Pro Server.  :-( 

Are you using this config 

<dict>
<key>INVITATION_STRING</key>
<string>$MOBILEDEVICEAPPINVITE</string>
<key>JSS_ID</key>
<string>$JSSID</string>
<key>SERIAL_NUMBER</key>
<string>$SERIALNUMBER</string>
<key>DEVICE_NAME</key>
<string>$DEVICENAME</string>
<key>MAC_ADDRESS</key>
<string>$MACADDRESS</string>
<key>UDID</key>
<string>$UDID</string>
<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>
<key>JSS_URL</key>
<string>your Jamf URL</string>
</dict>

note the UUID key which is not the same as the Jamf documentation, this worked for me and others.

Currently the config is without UDID. 
But I tested it too. Same like before...

do you have a / on the end of your URL if so try removing it.

So I was just able to get this working, I read another post where management_id and UDID still needs to be there...I've just tested on another iPad and it works as well.  After adding the App configuration, save it and then I deleted the app from device.  Went to that device and ran an update inventory so it will push out the Jamf Self-Service.  

Note please make sure you update the $JSS_URL with your jamfcloud URL 

<dict>
<key>INVITATION_STRING</key>
<string>$MOBILEDEVICEAPPINVITE</string>
<key>JSS_ID</key>
<string>$JSSID</string>
<key>SERIAL_NUMBER</key>
<string>$SERIALNUMBER</string>
<key>DEVICE_NAME</key>
<string>$DEVICENAME</string>
<key>MAC_ADDRESS</key>
<string>$MACADDRESS</string>
<key>MANAGEMENT_ID</key>
<string>$MANAGEMENTID</string>
<key>UDID</key>
<string>$UDID</string>
<key>JSS_URL</key>
<string>$JSS_URL/</string>
</dict>

Yes, I was just able to get this to work.

Thank you very much, 

VickiH

Also what helped was adding UDID back.  Not just management_id that seems to be working for me.  I hope you have a great day.

I've made the change, and new installs are working, but I'm not seeing the "Settings - Managed App Configuration" command going out to the existing devices. Is there an API command to force that?

Maybe you can try  the force update and see if that will help.